Start here — the LeadOcean API in one page

Quickstart

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.

Get your API key

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}'

200 OK · application/json

{
  "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.

Authentication

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. You can view, copy or rotate a key at any time in your account.

Agents connect differently. The MCP server uses OAuth 2.1 — your assistant signs in to your LeadOcean account and never sees a key. See MCP for agents.

Availability

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 693,080,309 people and 63,569,167 companies, built 2026-09-17. 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.

The rest of the documentation

Enrich a personEmail addresses, phone numbers and the full profile from a LinkedIn URL or work email.Company lookupFirmographics, detected technologies and metrics from a website domain.Contact endpointsWork email, personal addresses, phone numbers, and who a contact point belongs to — one question per endpoint.SearchPeople and company search: request shape, cursor paging, and what search returns.Filter referenceEvery people and company filter, its type and its allowed values — live from the API.Bulk CSV exportA people filter set to a plain .csv — up to 50,000 rows a request, priced in records, delivered with an email link.Records, limits and errorsHow usage is metered, what the rate limits are, and every status code.MCP for agentsConnect Claude, ChatGPT, Cursor, Codex and the rest over OAuth — no key to paste.API referenceEvery endpoint, generated live from the OpenAPI spec and runnable in the browser.

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.

NextEnrich a person