Offer PumpGTM to every user of your platform.
Your users' agents find real buyers. You hold one key, one account, and one bill. Each user gets their own workspace the first time their agent connects, and you see exactly what every user used.
Your PumpGTM account
billing@yourplatform.com · 4 users
MCP URL for acme_42
https://mcp.pumpgtm.com/mcp/u/acme_42
194 leads this month · billing: metered
Backed by Solo Founders Program
Y Combinator Spring 2026
21k stars on GitHub
#2 Product of the Day
“PumpGTM found exactly the right leads for my business and reaches out to them, automatically”
Your users get a sales team. You get one account.
Your product already knows who each customer sells to. PumpGTM lets each user's agent act on it, while you keep the account, the billing, and the controls.
What your users' agents can do
Find buyers
Agents describe who to reach in plain words. PumpGTM returns real people with titles, companies, LinkedIn URLs, and the reason each one matched.
LinkedIn and email outreach
Users connect their own LinkedIn and mailbox. Their agent drafts sequences, PumpGTM sends them at a human pace, and nothing goes out without approval.
Replies and meetings
PumpGTM follows every reply, drafts the answer, and books the meeting.
What you keep in one place
Billing
One partner account, one billing email, one bill. New accounts start with a free allowance of leads; when it runs out, the API returns a link for whoever owns your account.
User creation
No signup forms. Each user's workspace is created the first time their agent calls their URL, made from your own user id.
Usage
Every search and every lead is recorded against the user it ran for. Read it from one endpoint and show it in your own admin.
Limits
Cap any user's leads for the month, or switch a user off, with one API call.
Three calls. Your coding agent makes all of them.
Copy the prompt into Claude Code, Cursor, or Codex working in your repo. It reads the guide, signs you up, wires the URLs, and runs a test before it finishes.
POST /api/partner/v1/signup
{"email":"billing@yourplatform.com", ...}
→ 201 {"apiKey":"eve_mcp_…","freeLeads":50}Create your partner account
One request returns your key. Store it server side. That account is where billing lives.
https://mcp.pumpgtm.com/mcp/u/acme_42 Authorization: Bearer PUMPGTM_API_KEY
Give each user their own URL
Build it from your user id and connect their agent over MCP with your key. The first request creates their workspace.
GET /api/partner/v1/users
→ {"externalUserId":"acme_42","leadsFound":118,"monthlyLeadCap":250,"status":"active"}Read, cap, or disable any user
Usage per user from one endpoint. PATCH a monthly cap, DELETE to switch one off.
Built for teams running agents for other people.
Agent platforms
Harnesses where users deploy agents for many jobs. Sales becomes one more thing their agent can do.
Agencies
One account, a workspace for every client, usage per client.
Vertical SaaS
Your product already knows who the customer sells to. Let it act on that.
Internal tooling
A company running agents for its own sales team, under one key.
Questions platform teams ask.
The short answers, before your agent starts.
Do my users need a PumpGTM account?
No. You hold one account and one key. Each user gets a workspace under it, created the first time their agent connects. They never see PumpGTM unless you show it to them.
How does billing work?
Billing sits on your partner account, not on your users. New accounts start with a free allowance of leads. When it is used, find_people returns billing_required with a link for whoever owns your account, and the account endpoint shows the same link and the running total. Commercial terms are agreed with PumpGTM directly.
Is one user's data visible to another?
No. Every user has their own workspace. Searches, people, and leads never cross between users, or between partners.
What does my coding agent need to know?
Everything is in the technical guide at pumpgtm.com/mcp/platforms.md: the signup call, the URL pattern, the tools, the errors, and a test to run before finishing. The prompt on this page points the agent at it.
Which MCP clients work?
Any client that takes a URL and a bearer token: the official SDKs, Anthropic's MCP connector, Claude Code, Cursor, Codex. No custom auth.
Can a user connect their own LinkedIn?
That is the next release for platforms. Direct PumpGTM customers already do it at pumpgtm.com/mcp, and the same flow opens outreach tools for a partner's user once we ship the hand-off.
How do I know it works?
The prompt ends with a test: list the tools, run one real search for a test user, and read that user's usage back. Your agent shows you all three before it finishes.
Your coding agent can have this running in a few minutes.
Prefer to read first? The technical guide has every call. Questions: hello@pumpgtm.com