The GTM data API · one price, no credits
Search, enrich and verify people and companies through one REST API — and a hosted MCP server, so Claude, ChatGPT and your own agents can do it themselves. One price, no CRM to migrate to, no seats to buy and no credits to top up.
Free to start · no credit card · 1,000 records to spend whenever you like · cancel any time
Real commands from our docs. Records shown are samples, not real people.
Unified from 20+ data sources into one schema — one key, one shape, no vendors to stitch together yourself.
Works where you work
LeadOcean runs a hosted MCP server. Add it once, sign in with your account, and your assistant can enrich and verify people and companies while it works — usage billed to your plan, not to a key you pasted into a chat. Everything the tools do is available over plain REST too.
Add LeadOcean as a custom connector in Claude web, desktop or mobile, then enrich and verify inside any conversation.
Set upTurn on developer mode, add the MCP server URL, approve the sign-in, and give your GPTs fresh B2B data.
Set upClaude Code, Cursor, Codex, VS Code, Windsurf and Gemini CLI all connect over remote MCP with one line of config.
Set upThree REST endpoints, one JSON schema, cursor paging. Call it from a script, a workflow, a warehouse job or your product.
Set upWho it is for
LeadOcean is an API and a set of tools for agents. If your pipeline lives in scripts, workflows and prompts rather than in someone else's interface, this is the data layer for it.
Build lists, enrich records and keep fields fresh from your own jobs — on your schedule, in your warehouse, with your logic.
Turn a list of profiles or domains into contactable records — verified work emails and phone numbers, checked before you ever send. Segment building by title, seniority, country, industry and company size arrives with search.
Give an agent the 12 MCP tools and it qualifies and enriches on its own — inside Claude, ChatGPT, Cursor or your product.
One key, many clients. Predictable JSON, cursor paging and a schema that stays stable while you scale delivery.
Build once, use anywhere
Search an ICP, enrich a person, look up a company. Structured, predictable JSON that code and models both read well — plus llms.txt, so an assistant can learn the entire API in a single fetch.
curl -X POST "https://api.leadocean.io/v1/people/enrich" \
-H "x-api-key: $LEADOCEAN_API_KEY" \
-H "content-type: application/json" \
-d '{"linkedin_url":"https://www.linkedin.com/in/jane-doe","reveal_email":true}'{
"success": true,
"data": {
"profile_data": {
"profile_full_name": "Sarah Chen",
"profile_headline": "Founder & CEO at CloudSync",
"profile_url": "https://www.linkedin.com/in/…"
},
"contact_data": {
"has_email": true,
"email_status": "verified",
"contact_emails": [
{ "email": "sarah@cloudsync.com", "type": "work", "status": "verified" }
],
"contact_phones": [
{ "phone": "+1 415 555 0189", "type": "mobile" }
],
"contact_current_experiences": [{
"company_name": "CloudSync",
"company_domain": "cloudsync.com",
"job_title": "Founder & CEO",
"company_employees": { "number_of_employees": 120 }
}]
}
},
"meta": { "credits": 1, "source": "own" }
}Everything you need
50 ICP filters across people and 34 across companies — title, seniority, industry, headcount, revenue, funding, tech and location, plus email status, email type and reachability. Cursor paging, a stable response envelope, and the same schema the enrichment endpoints return.
Live today. A LinkedIn URL or an email becomes a full record: current role, company firmographics, work history, skills, education, location — plus every verified work email and phone number we hold, at no extra record.
Deliverability status on every email, and reveal the address only when you actually need it — so a bad list never costs you twice.
Twelve self-describing MCP tools plus a complete llms.txt reference, so a model can plan and run the work without you writing glue.
From incomplete to AI-ready
Send what you have — an email or a LinkedIn URL. Get back a structured record with the context your play needs to run, and nothing invented: unknown fields come back null instead of guessed.
Simple, transparent pricing
Every account starts free with 1,000 records and no card — a one-off allowance, not a monthly one. Go to production and one plan covers everything, without a meter you have to watch: unlimited searches, enrichments and lookups. No credit packs, no per-record pricing, no overage invoices, no sales call.
1,000 records to spend whenever you like — one-off, not monthly — plus the full API and the MCP server. No card, no trial clock, no feature gates.
No credit card required. Upgrade whenever you like.
Questions
Create an account, copy your key, and make your first call in under a minute.
Free to start · no credit card · 1,000 records to spend whenever you like · cancel any time