Documentation
Search, enrich and verify people and companies over REST, or let an agent do it through the hosted MCP server. One key, one schema, 996M profiles, 424M people with an email address. Base URL https://api.leadocean.io
Create an account and a key is waiting for you — no card, and 1,000 records to spend whenever you like — a one-off allowance, not a monthly one. Send it as the x-api-key header and make your first call.
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" }
}That is person enrichment. Company lookup works the same way from a domain, and search uses the same key and the same record shape.
Every request carries your key in the x-api-key header. Keys have scopes: enrich covers /v1/people/enrich and /v1/companies/enrich, search covers /v1/people/search, /v1/companies/search and the free /v1/companies/count. GET /v1/account answers with either scope and tells you everything about the account the key spends: plan, records used and left, when they reset, export windows and rate. You can view, copy or rotate a key at any time in your account.
Enrichment answers today. /v1/people/enrich and /v1/companies/enrich are served from our own store and return live data.
Search is live. /v1/people/search and /v1/companies/search answer from an index of 996,165,074 people and 73,728,117 companies, as of 2026-11-13. Page with meta.nextCursor, passing it back exactly as it was handed to you; one record is counted per person returned, and a page is capped to what is left in your month. One search pages to 10,000 rows by default — see how deep one search can page.
Sizing is free. GET /v1/companies/count answers how many companies match, with breakdowns by industry, headcount, country, state and NAICS, and spends nothing; count=true&limit=1 on the people search does the same for people, with how many employers they span. See count companies.
Everything here is also published as plain Markdown for models: llms.txt and llms-full.txt are generated from the running API, so they never drift from it.