LeadMarmot API
The daily file as JSON: the companies that just raised or launched, what each needs most, the opener, and the contact paths. The API returns the same rows a member receives by email, nothing less.
Quick start
No key needed for the sample: ten real leads from a recent file.
curl "https://leadmarmot.com/api/v1/leads?sample=1"
With your key, the latest file:
curl -H "Authorization: Bearer YOUR_KEY" "https://leadmarmot.com/api/v1/leads"
Your key
Every member has one key, and it works from the first minute of the 7-day trial. You find it in three places: on the welcome page right after you sign up, on your list page under "Your agent and the API", and in every LeadMarmot email.
Send it as a header, Authorization: Bearer YOUR_KEY, or as ?key=YOUR_KEY where a tool cannot set headers.
Requests
One endpoint, GET /api/v1/leads, and a few parameters.
| Parameter | What it returns |
|---|---|
| (none) | The latest file. |
| date=YYYY-MM-DD | The file of one day. |
| since=YYYY-MM-DD | Every lead since that day, newest first. |
| need=GEO | Only leads with this need: GEO, SEO, content, paid/CRO, PR/social, technical. |
| company=acme.com | One company, by website or name: its most recent record. |
| limit, offset | 50 rows by default, 500 at most. Page with offset. |
| sample=1 | Ten sample leads. No key. |
| stats=1 | How many leads the last seven days hold. No key. |
GET /api/v1/leads?since=2026-11-01&need=GEO&limit=200 GET /api/v1/leads?date=2026-11-06 GET /api/v1/leads?company=yk-robotics.com
Response
A day returns { "date", "leads": [...] }. A range returns { "since", "to", "count", "leads": [...] }. One lead, shortened:
{
"signal_date": "2026-10-29",
"company": "YK-Robotics",
"website": "yk-robotics.com",
"signal": "raised $1.1M Seed",
"round": "Seed",
"amount": "$1.1M",
"needs": "GEO, paid/CRO, SEO, PR/social",
"top_need": "GEO",
"hook": "YK-Robotics raised $1.1M Seed on 2026-10-29. When their buyer asks ChatGPT \"What software helps system integrators program robotic cells across multiple robot brands?\", it answers RoboDK, not YK-Robotics.",
"contact_email": "info@yk-robotics.com",
"email_type": "role",
"email_verified": "role_account",
"linkedin": "https://www.linkedin.com/company/yk-robotics",
"contact_form": "https://www.yk-robotics.com/contacts",
"buyer_question": "What software helps system integrators program robotic cells across multiple robot brands?",
"chatgpt_recommends_them": "no",
"rival_chatgpt_names": "RoboDK",
"analytics": "no",
"customer_proof": "no",
"what_they_sell": "AI-powered robotic cell software for system integrators and manufacturers."
}
Fields
| Field | Meaning |
|---|---|
| signal_date | The day the company raised or launched. |
| company, website | Who it is. |
| signal | What happened, in words: "raised $1.1M Seed", "launched". |
| round, amount | The round and its size, when it is a raise. |
| country, sector, what_they_sell | Where, in which field, and the product in one sentence. |
| hiring, pricing | "yes" when the site has a careers page or a pricing page. |
| needs, top_need | What the company needs, strongest first: GEO, SEO, content, paid/CRO, PR/social, technical. |
| hook | The opening line: the fact about their own business that makes the need plain. |
| contact_email | The company's shared mailbox (info@, hello@), when its site shows one. Never a named person's address. |
| email_type | "role" when contact_email is filled. "named" when the site shows a named person's address instead: the file leaves it out, and the person is one click away on the company's site. |
| email_verified | The verifier's verdict: safe, role_account, catch_all, or empty when unchecked. |
| linkedin, contact_form, x_handle | The other ways in. |
| buyer_question | The question their buyer asks an AI assistant. |
| chatgpt_recommends_them | Whether ChatGPT names them for that question. |
| rival_chatgpt_names | Who it names instead. |
| pages_chatgpt_reads | The pages its answer was built from. |
| claude_recommends, gemini_recommends | The same verdict from the other two assistants, when checked. |
| google_own_name_rank | Where their own site ranks for their own name. |
| analytics | Whether the site carries an analytics tag or an ad pixel. |
| content_engine, site_pages | Whether they publish, and how many pages the site has. |
| customer_proof | Whether the site shows customers, logos or testimonials. |
| ai_crawlers_blocked, meta_and_og | Technical checks: AI crawlers blocked in robots.txt, title and share tags present. |
Limits
The API serves the last 30 days. A new file lands every morning. Each key can make 60 requests a minute; every response says where you stand in X-RateLimit-Limit and X-RateLimit-Remaining.
Errors
Errors are JSON: { "error": "...", "docs": "https://leadmarmot.com/docs" }.
| Status | When |
|---|---|
| 400 | A date that is not YYYY-MM-DD, or older than the last 30 days. |
| 401 | No key, a wrong key, or a membership that has ended. |
| 429 | More than 60 requests in a minute. Retry-After says when to come back. |
MCP server
The same data as tools an agent can call. Add this URL as an MCP server in Claude, ChatGPT or Cursor:
https://leadmarmot.com/mcp?key=YOUR_KEY
It speaks JSON-RPC over POST (Streamable HTTP) and also accepts the key as a Bearer header. Three tools:
| Tool | What it does |
|---|---|
| sample_leads | Ten sample leads. No key. |
| leads | The leads of one day, with optional date, need and limit. |
| lead | One company's full record, by name or website. |
Guides
Step by step for lemlist, Instantly, Smartlead, Clay, Zapier, Make and HubSpot: all guides.
Compare
How LeadMarmot compares with Clay, Dealroom, Harmonic, Growth List, Fundz, doing it yourself and others.