Enrich a person from a LinkedIn URL, email or phone

What you get

Person enrichment returns one record in the leadocean.person.v1 schema: who the person is, their current role, and how to reach them. Contact points come back only when you set reveal_email: true. A value we do not hold is null, never guessed.

has_email and has_phone answer whether or not you reveal. That lets you check a person is worth a record before you ask for the address.

What you send

Send exactly one identifier. Two is a 400. There is no lookup by name and company. Search by domain first, then enrich by person_id.

Three ways to run it

In the app

Yes, in bulk. The Exports page at app.leadocean.io builds a people list from filters, and its column picker includes the enrich fields: email_N_address, email_N_status, phone_N_number, current_job_title and more. It shows the record price before you start and gives you a CSV. For one named person, use the API or an agent.

With the API

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

A hit returns success: true, the data object above and meta.credits: 1. GET works too, with the same fields as query parameters.

The old POST /v1/people/enrich still answers but is deprecated.

From an AI agent

The MCP tool is leadocean_get_lead. It takes the same four identifiers. Try: "Enrich linkedin.com/in/jane-doe and give me the work email, its status and her current title." Setup is in Enrich Person over MCP. The packaged steps are in the Enrich Person skill. To push results into a CRM, see the Pipedrive enrichment recipe.

What it costs

One person found is 1 record, with or without reveal_email. A 404, meaning we hold nothing for that person, costs nothing. Rejected requests (429, 402, 503) are never metered. Over MCP, a leadocean_get_lead that finds nobody is free too.

Free gives you 1,000 records, one-off, no card. Pro is $499 a month, flat, with no per-record price, inside fair use. See pricing.

Worked example: you enrich 10,000 people and 7,000 are found. That is 7,000 records, and the 3,000 misses cost nothing. Free covers the first 1,000 once. On Pro the month is $499 whatever the count.

Coverage

LeadOcean holds 693M people. Of those, 366M have an email and 166M have a phone (measured 2026-09-23). Roughly one person in five has no LinkedIn URL, so about a fifth of the database can only be reached by person_id. The dataset is refreshed monthly, and each record carries its own fetched_at date.

Accuracy and limits

• Read email_status before you send. verified and catch_all_valid are the ones to send to. invalid, spam_trap, abuse and disposable are drops. risky, role and derived are your call. untested is not a negative signal.
• Read email_type too. work is the current employer. work_other is usually a former one and the likeliest to bounce.
• No refund for bounces. Check the status first.
• Do-not-call is not answered. dnc is published but not populated. Null means unknown, never safe to call. Run your own check.
• Dates are batch dates. verified_batch_date is the verification run, not a timestamp for that address. Null does not mean unverified.
• Career history is thin. The MCP tool description says resume_data comes back empty from the current source. Do not build on it.
• Rate limit. 100 requests per second per key, on every plan.
• Errors. 400 validation, 401 bad key, 403 missing scope, 404 not in our data, 429 too fast, 503 store unreachable and never billed.

FAQ