PumpGTM people data: build the context behind your next customer

A LinkedIn URL is a useful starting point. Before you put someone into a sales workflow, you usually need more: their current company, a work email, and enough context to understand who they are.

We’re opening that part of PumpGTM through the people data index. You can look up a person through our API or your connected AI agent and use the result in your own tools.

The page includes an interactive example: switch between an API and MCP call, then watch the result become a readable person profile. You can inspect the same response as JSON.

One profile, useful context

Start with a public LinkedIn person URL. PumpGTM resolves the professional profile and returns the name, headline, location, current company, and role when available. Ask for a work email and it runs the lookup behind the same request.

The response keeps missing fields empty. It tells you when the profile was only partially enriched, when an email could not be found, and whether an email's domain matches the resolved company. Finding an address does not guarantee delivery.

curl https://app.pumpgtm.com/api/v1/people/enrich \
  -H "Authorization: Bearer $PUMPGTM_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "linkedinUrl": "https://www.linkedin.com/in/namanyayg",
    "includeWorkEmail": true
  }'

The API docs cover authentication, response fields, Energy, and errors. Your existing workspace key works here too.

People have social context

We also have social connection data from permitted public observations. Where available, the response connects a person's public social profiles and returns observed follow relationships with their direction, source, and observation time.

That distinction matters. A public link between two accounts is evidence that connects them. A matching name alone is not. A follow tells you that one account followed another; it does not establish friendship or a warm introduction.

Coverage varies by person. An empty response means we have no available evidence. The launch API reads existing social observations; it does not build a new, complete network on demand.

Start with a ready dataset

You do not have to start with an empty list. Our YC founder dataset includes 11,517 founders from the public YC directory, with the LinkedIn and X profiles they listed. You can filter the list by batch, role, industry, and more.

Our early-stage investor dataset contains 520 investor contacts and public LinkedIn profiles, organized around funds backing YC and early-stage companies.

These are existing dataset snapshots you can browse today. Pick a public profile, enrich it, and bring the result into your own CRM or workflow. Work-email enrichment is a separate lookup; not every listed person has every contact field.

Your agent can make the same call

Connect to https://mcp.pumpgtm.com/mcp and ask your agent to enrich a profile. The enrich_person tool runs the same operation as the REST API and returns the same structured data and Energy usage.

Read the people MCP guide for the tool call and connection instructions. There is no new people-data screen to learn inside the app.

Build with Energy

People-data lookups spend the Energy in your PumpGTM workspace. One Energy is $0.05. Profile lookup and optional email enrichment are metered separately, and each response reports both Energy spent and any amount still held for unresolved provider costs.

A paid lookup can cost Energy even when it finds no match. Check the usage details before building an automated workflow, and do not automatically retry a paid call after a timeout.

Distribution and data, together

PumpGTM already helps sales teams find buyers and run outreach. Opening our people data gives teams another way to build on that work: use our data inside an agent, a CRM, or a workflow you own.

The first release uses our existing profile lookup and email-provider waterfall. We can improve the underlying coverage while keeping one public API and MCP contract for the teams building on it.

Enrichment returns data. Sending messages remains a separate action. That lets you decide how the data fits into your sales process.

Explore the people data index, or make your first API call.