---
name: orthogonal-leadocean
description: "Call LeadOcean through Orthogonal's pay-per-use Run API: B2B people and company data: search ~996M people and 73M companies by filter, enrich one person or company into a full profile, look up a person's work email, personal emails or phone numbers, find who holds an email or phone, and size markets for free."
---

# LeadOcean — Orthogonal API

> Pay-per-use API on Orthogonal. Each call is billed to your Orthogonal balance.
> Base API: `https://api.orthogonal.com/v1/run` · [llms.txt](https://www.orthogonal.com/llms.txt) · [browse all APIs](https://www.orthogonal.com/catalog)

B2B people and company data: search ~996M people and 73M companies by filter, enrich one person or company into a full profile, look up a person's work email, personal emails or phone numbers, find who holds an email or phone, and size markets for free.

**Verified:** no

## Access

**Run API:** `POST https://api.orthogonal.com/v1/run`
**Auth:** `Authorization: Bearer $ORTHOGONAL_API_KEY`
Get an API key at https://www.orthogonal.com/account/keys

No account or key yet? Set up Orthogonal first with https://www.orthogonal.com/skill.md: it covers the CLI, the MCP server, the TypeScript SDK and sign-up, including an agent sign-up without a password (https://www.orthogonal.com/agent-signup.md).

Every call goes through the unified Run API: send the API `slug`, the endpoint `path`, and the `query`/`body` parameters. The response is `{ "success": true, "priceCents": <US cents>, "requestId": "...", "data": { ... } }`.

Quote first, free: the same request with `"dryRun": true` returns the price without calling the API or charging anything. On a retry after a timeout, send the same `Idempotency-Key` header so the call runs and bills once.

## Endpoints

### Work email lookup

Returns ONE address, or `data: null`. STABLE — the shape, the prices and the rules behind the data are all promises now. Returns only addresses at the person's CURRENT employer's domain (email type `work`) whose deliverability was actually checked (`verified`), whose mailbox we confirmed on a catch-all domain (`catch_all_valid`), or whose domain accepts everything (`catch_all`). A former employer's address (`work_other`) is never returned here, and neither is an address nobody has tested — so `data: null` means "none that qualify", not "no work email" — this door has no `found` field, and no `meta`, so `at_current_employer` is not reported; Each address carries verified_batch_date, the run we checked it in; null there means the check was not ours, NOT that it is unverified. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: th

`GET /v2/people/email/work`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/13047618-7ff7-4d73-b8ee-09f15cfc8997

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No | A personal LinkedIn profile URL (linkedin.com/in/...). |
| `contact_id` | string | No | The numeric id a people-search row carries at meta.source_ids.person_id. `person_id` is accepted as the same field under its original name; send one of the two, never both. |
| `person_id` | string | No | The original name of contact_id. Identical behaviour. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/email/work","method":"GET","query":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Work email lookup (JSON)

Returns ONE address, or `data: null`. STABLE — the shape, the prices and the rules behind the data are all promises now. Returns only addresses at the person's CURRENT employer's domain (email type `work`) whose deliverability was actually checked (`verified`), whose mailbox we confirmed on a catch-all domain (`catch_all_valid`), or whose domain accepts everything (`catch_all`). A former employer's address (`work_other`) is never returned here, and neither is an address nobody has tested — so `data: null` means "none that qualify", not "no work email" — this door has no `found` field, and no `meta`, so `at_current_employer` is not reported; Each address carries verified_batch_date, the run we checked it in; null there means the check was not ours, NOT that it is unverified. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: th

`POST /v2/people/email/work`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/74e9725b-3ce1-419b-8010-97cbeadd192f

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `contact_id` | string | No |  |
| `person_id` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/email/work","body":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Personal email lookup

Returns a LIST, with no status field. STABLE — the shape is a promise. Every personal address (webmail and similar) we hold and do not know to be bad. A verified-only door would return almost nothing here while looking as though it had searched — our verifier has never tested a personal address, not one. The status is APPLIED rather than published: invalid, spam_trap, abuse, disposable, risky and role are WITHHELD, because a door with no status field leaves a caller nothing to be careful with. Each address carries `email` and `verified_batch_date`, and nothing else. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: the throttle is reported in headers on every response (X-Quota-State, X-Quota-Reset, X-Quota-Contact, X-RateLimit-Limit), so no meta key is needed to carry it. /v2/people/reverse still returns meta. Costs one recor

`GET /v2/people/email/personal`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/95286cce-1568-49d1-b60a-1c93b69f9f85

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No | A personal LinkedIn profile URL (linkedin.com/in/...). |
| `contact_id` | string | No | The numeric id a people-search row carries at meta.source_ids.person_id. `person_id` is accepted as the same field under its original name; send one of the two, never both. |
| `person_id` | string | No | The original name of contact_id. Identical behaviour. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/email/personal","method":"GET","query":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Personal email lookup (JSON)

Returns a LIST, with no status field. STABLE — the shape is a promise. Every personal address (webmail and similar) we hold and do not know to be bad. A verified-only door would return almost nothing here while looking as though it had searched — our verifier has never tested a personal address, not one. The status is APPLIED rather than published: invalid, spam_trap, abuse, disposable, risky and role are WITHHELD, because a door with no status field leaves a caller nothing to be careful with. Each address carries `email` and `verified_batch_date`, and nothing else. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: the throttle is reported in headers on every response (X-Quota-State, X-Quota-Reset, X-Quota-Contact, X-RateLimit-Limit), so no meta key is needed to carry it. /v2/people/reverse still returns meta. Costs one recor

`POST /v2/people/email/personal`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/57633cf1-988e-49a5-9b55-a69a4d993f30

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `contact_id` | string | No |  |
| `person_id` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/email/personal","body":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Phone number lookup

STABLE — the shape is a promise. Every number we hold for the person, best first; the position in the array is the priority. Each number is just `phone` and `type` (mobile, direct, office). v2 does NOT publish `dnc`: it is unpopulated at source, and a field that looks like a compliance answer while carrying none is a trap either way — its absence here is not clearance any more than v1's null was. To find people who have a number before spending anything, search with hasPhone=true. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: the throttle is reported in headers on every response (X-Quota-State, X-Quota-Reset, X-Quota-Contact, X-RateLimit-Limit), so no meta key is needed to carry it. /v2/people/reverse still returns meta. Costs one record, the same as an enrichment, because it is the same lookup — including when the answer

`GET /v2/people/phone`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/c3785442-c369-45ca-8368-5bc70cf39091

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No | A personal LinkedIn profile URL (linkedin.com/in/...). |
| `contact_id` | string | No | The numeric id a people-search row carries at meta.source_ids.person_id. `person_id` is accepted as the same field under its original name; send one of the two, never both. |
| `person_id` | string | No | The original name of contact_id. Identical behaviour. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/phone","method":"GET","query":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Phone number lookup (JSON)

STABLE — the shape is a promise. Every number we hold for the person, best first; the position in the array is the priority. Each number is just `phone` and `type` (mobile, direct, office). v2 does NOT publish `dnc`: it is unpopulated at source, and a field that looks like a compliance answer while carrying none is a trap either way — its absence here is not clearance any more than v1's null was. To find people who have a number before spending anything, search with hasPhone=true. This endpoint returns `data` and NO `meta` object. The price is unchanged at one record per call but is not reported per call - read GET /v1/usage for it. There is NO exception, including for a throttled account: the throttle is reported in headers on every response (X-Quota-State, X-Quota-Reset, X-Quota-Contact, X-RateLimit-Limit), so no meta key is needed to carry it. /v2/people/reverse still returns meta. Costs one record, the same as an enrichment, because it is the same lookup — including when the answer

`POST /v2/people/phone`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/93b147aa-5243-47d2-b37e-ea844b6f51b4

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `contact_id` | string | No |  |
| `person_id` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/phone","body":{"linkedin_url":"<string>","contact_id":"<string>","person_id":"<string>"}}'
```

### Reverse email/phone lookup

STABLE — the shape is a promise. The reverse of the three lookups above: send an email address or a phone number and get the person who holds it, plus that point's own type, status and check date. Returns the identity rather than the full profile — for everything we know about the person, call /v1/people/enrich, which is the same price and answers from the very same cached record this call populates. matched_in_record distinguishes "the record echoes this exact point back" from "the record was matched on it upstream but does not list it", so a null matched is never read as "nobody found". Costs one record, the same as an enrichment, because it is the same lookup — including when the answer is found:false. Asking whether a person HAS a deliverable address is free: a people-search row publishes has_email, email_status and email_type as flags, and sizing a search spends nothing however often you ask.

`GET /v2/people/reverse`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/cc915ca6-7a9c-4949-98a9-e33b9460d544

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `email` | string | No | An address to look up. Send this OR phone, never both. |
| `phone` | string | No | A number to look up, in any common format. Send this OR email, never both. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/reverse","method":"GET","query":{"email":"<string>","phone":"<string>"}}'
```

### Reverse lookup (JSON)

STABLE — the shape is a promise. The reverse of the three lookups above: send an email address or a phone number and get the person who holds it, plus that point's own type, status and check date. Returns the identity rather than the full profile — for everything we know about the person, call /v1/people/enrich, which is the same price and answers from the very same cached record this call populates. matched_in_record distinguishes "the record echoes this exact point back" from "the record was matched on it upstream but does not list it", so a null matched is never read as "nobody found". Costs one record, the same as an enrichment, because it is the same lookup — including when the answer is found:false. Asking whether a person HAS a deliverable address is free: a people-search row publishes has_email, email_status and email_type as flags, and sizing a search spends nothing however often you ask.

`POST /v2/people/reverse`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/5f6c98c0-f5e1-4c05-b1b9-498301bc7f25

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `email` | string | No |  |
| `phone` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v2/people/reverse","body":{"email":"<string>","phone":"<string>"}}'
```

### Person phone finder (v1)

Send exactly one identifier. Returns has_phone plus every number we hold, best first, each with its type. Costs one record — the same as an enrichment, because it is the same lookup. To find people who HAVE a number before spending anything, search with hasPhone=true. has_phone: false means we hold none, not that the lookup failed. dnc is published on every number but is not yet populated: null means unknown, never "safe to call".

`GET /v1/people/phone`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/4733592e-310f-457c-91c8-99179a8a4438

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `email` | string | No |  |
| `phone` | string | No | A number you already hold, to find the rest we have for that person. |
| `person_id` | string | No | The id a people-search row carries at meta.source_ids.person_id — send it back to enrich that exact person without having carried an identifier between the two calls. It is a translation rather than a fourth key: we look the person up by id and then enrich the identifier their own record holds (their email, or their LinkedIn URL when we hold no address for them — email is preferred, because it is what this cohort has and because it round-trips back to the same person), so the answer, the one rec |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/phone","method":"GET","query":{"linkedin_url":"<string>","email":"<string>","phone":"<string>","person_id":"<string>"}}'
```

### Person phone finder (v1, JSON)

JSON-body form of GET /v1/people/phone: send exactly one identifier (linkedin_url, email, phone or person_id) and get has_phone plus every number held, best first. Costs one record.

`POST /v1/people/phone`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/f86a0f17-a8a9-4e67-921f-f0de3cedd0b2

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `email` | string | No |  |
| `phone` | string | No |  |
| `person_id` | string | No | The id a people-search row carries at meta.source_ids.person_id — send it back to enrich that exact person without having carried an identifier between the two calls. It is a translation rather than a fourth key: we look the person up by id and then enrich the identifier their own record holds (their email, or their LinkedIn URL when we hold no address for them — email is preferred, because it is what this cohort has and because it round-trips back to the same person), so the answer, the one rec |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/phone","body":{"linkedin_url":"<string>","email":"<string>","phone":"<string>","person_id":"<string>"}}'
```

### Person enrichment

Send exactly one identifier. Costs one record; reveal_email adds every email and phone we hold at no extra charge.

`GET /v1/people/enrich`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/7fb9e9ae-d648-4d85-90c8-f81c7df7cb06

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `email` | string | No |  |
| `phone` | string | No | Any human format; the source parses it. |
| `person_id` | string | No | The id a people-search row carries at meta.source_ids.person_id — send it back to enrich that exact person without having carried an identifier between the two calls. It is a translation rather than a fourth key: we look the person up by id and then enrich the identifier their own record holds (their email, or their LinkedIn URL when we hold no address for them — email is preferred, because it is what this cohort has and because it round-trips back to the same person), so the answer, the one rec |
| `reveal_email` | boolean | No | Left out: true when you look the person up by email, false otherwise. No extra record either way. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/enrich","method":"GET","query":{"linkedin_url":"<string>","email":"<string>","phone":"<string>","person_id":"<string>","reveal_email":"<boolean>"}}'
```

### Person enrichment (JSON)

JSON-body form of GET /v1/people/enrich: send exactly one identifier (linkedin_url, email, phone or person_id) for the full person profile. Costs one record; reveal_email adds every email and phone held at no extra charge.

`POST /v1/people/enrich`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/ca461bfd-b983-4f7a-afe7-fe92a6894b9f

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `linkedin_url` | string | No |  |
| `email` | string | No |  |
| `phone` | string | No |  |
| `person_id` | string | No | The id a people-search row carries at meta.source_ids.person_id — send it back to enrich that exact person without having carried an identifier between the two calls. It is a translation rather than a fourth key: we look the person up by id and then enrich the identifier their own record holds (their email, or their LinkedIn URL when we hold no address for them — email is preferred, because it is what this cohort has and because it round-trips back to the same person), so the answer, the one rec |
| `reveal_email` | boolean | No | Left out: true when you look the person up by email, false otherwise. No extra record either way. |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/enrich","body":{"linkedin_url":"<string>","email":"<string>","phone":"<string>","person_id":"<string>","reveal_email":"<boolean>"}}'
```

### People search

Each person returned counts one record. Page with meta.nextCursor. One search pages through at most 10,000 rows by default; past that no further cursor is issued and meta.depthCapped is true. The figure is per account — support can raise it for a genuine large export, so ask rather than working around it. It counts rows paged through and is not the monthly records allowance, which is separate. The answer to a capped walk is to narrow the filters and run several smaller searches; paging harder returns no more cursors. A walk of the WHOLE result set is order=stable: id order, on the snapshot the first page read (a 410 means that snapshot was retired mid-walk — start again without a cursor); an account enabled for unlimited walks pages it to its end, up to 200 rows a page, while every other account keeps the depth above and 100 rows.

`GET /v1/people/search`

**Estimated cost:** Dynamic — use `"dryRun": true` in the Run API request to check the exact cost before calling.

**Page:** https://www.orthogonal.com/api/leadocean/2c5119f4-8c74-48a4-801b-8bc80a8f9495

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over the person: name, title, headline, profile summary, skills, job descriptions, and their company name |
| `profileKeywords` | string | No | the same as keywords — the person’s own profile text; kept under this name for clients that adopted it |
| `excludeProfileKeywords` | string | No | profile keywords to exclude |
| `title` | string | No | job title keywords; wrap a value in [brackets] for an exact match |
| `excludeTitle` | string | No | job titles to exclude |
| `excludeViewed` | boolean | No | leave out the people this account marked viewed (POST /v1/people/viewed) in viewedSet; exact for a list up to 20,000, a skip-ahead walk beyond (see meta.excludedViewed, meta.walkCapped) |
| `viewedSet` | string | No | which viewed list excludeViewed reads, e.g. one per end-client workspace; default "default" |
| `excludeIds` | string | No | person_ids to leave out of the results, e.g. ones you already showed; max 1,000 |
| `seniority` | string | No | LeadOcean seniority band (mapped onto job_level upstream) |
| `jobLevel` | string | No | seniority band as the data source defines it |
| `jobFunction` | string | No | department or function of the current role |
| `country` | string | No | where the person is located |
| `continent` | string | No | continent the person is in |
| `salesRegion` | string | No | commercial region the person is in |
| `city` | string | No | city keywords for the person |
| `excludeCity` | string | No | cities to exclude |
| `education` | string | No | school, degree or year phrases |
| `minConnections` | integer | No | minimum LinkedIn connections, 0–500 — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `domain` | string | No | company domain the person works at |
| `companyName` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeCompanyName` | string | No | company name phrases to exclude; [brackets] for exact |
| `companyLinkedin` | string | No | company LinkedIn URLs |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket; coarser and faster than minEmployees/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minFounded` | integer | No | year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `fundingType` | string | No | type of the last funding round — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `minFunding` | integer | No | total funding raised, USD — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `investors` | string | No | lead investor keywords — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `sic` | string | No | SIC codes of the employer — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `naicsSector` | string | No | two-digit NAICS sector of the employer as STORED on the person record (a SIC crosswalk from the source): the first-listed sector, held for about half of people, as of the last people build — applies directly, never dropped. It can differ from the company record’s derived company_data.naics_sector |
| `keywords` | string | No | keywords in the person’s own profile: headline, summary, skills and job descriptions — the PERSON’s text, not the employer’s (for the company’s text search companies, or filter people by industry / companyName). Each value is a phrase whose words must all appear; several values OR together |
| `excludeKeywords` | string | No | profile keywords to exclude |
| `companyKeywords` | string | No | what the EMPLOYER does, in its own words: each value is a phrase whose words must all appear in the company’s description, specialties, tags or name — or an exact industry label, which then matches every company filed under it; several values OR together. The broad way to ask for "people at cybersecurity companies": an industry label alone misses most of them — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | technologies detected on the company website (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `emailStatus` | string | No | email deliverability (own data only) |
| `emailType` | string | No | work or personal email (own data only) |
| `hasEmail` | boolean | No | only people with, or without, a known email (own data only) |
| `hasPhone` | boolean | No | only people with, or without, a known phone number (own data only) |
| `reachable` | string | No | holding an email OR a phone — `strict` additionally requires the email to be verified, catch_all_valid or catch_all |
| `cursor` | string | No | Opaque page token: pass back exactly the string meta.nextCursor returned, unchanged. Cursors are signed — one that has been edited, truncated or hand-built is refused with 400 "Invalid cursor", as is one minted for a different search. A cursor is a position in one walk rather than a handle on a result set: do not store it, restart the query instead. Cursors issued before 2026-09-19 no longer verify. |
| `limit` | integer | No | records per page, 1–100 (an account enabled for unlimited walks may ask up to 200 on order=stable) |
| `facets` | boolean | No | also return counts by seniority, country, industry and company size |
| `facetCompanies` | boolean | No | also count distinct employers inside each facet bucket (an estimate within ~1%); slower on a wide filter, so off by default — meta.distinctCompanies at the top level comes with every filtered count (null with no filter at all) |
| `slim` | boolean | No | drop empty and heavy parts of each record (picture block, duplicate lists); default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. profile_data.profile_full_name,meta.source_ids; everything else is omitted |
| `order` | string | No | ranked (default): best matches first. stable: every match in id order (person_id / company_id), unscored, on the index snapshot the first page read — for walking a whole result set. Pass order=stable with every page: a stable cursor only continues a stable walk, and a ranked cursor only a ranked search. If the snapshot is retired mid-walk the next page answers 410; start the walk again without a cursor. An account enabled for unlimited walks pages a stable walk to its end, with no depth cap, up |
| `count` | boolean | No | Also return the exact total number of matches in meta.total. On the PEOPLE search it is opt-in because it is work: a page is ranked either way, a total has to be tallied. The COMPANY search counts its first page regardless and carries the figure in the cursor, so every page of a company walk has meta.total without recounting. FREE WITH limit=1: that combination is a sizing call, costs no records however often you send it, and answers with an empty `data` and `meta.countOnly: true` — the number i |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/search","method":"GET","query":{"q":"<string>","profileKeywords":"<string>","excludeProfileKeywords":"<string>","title":"<string>","excludeTitle":"<string>","excludeViewed":"<boolean>","viewedSet":"<string>","excludeIds":"<string>","seniority":"<string>","jobLevel":"<string>","jobFunction":"<string>","country":"<string>","continent":"<string>","salesRegion":"<string>","city":"<string>","excludeCity":"<string>","education":"<string>","minConnections":"<integer>","domain":"<string>","companyName":"<string>","excludeCompanyName":"<string>","companyLinkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","minFollowers":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","sic":"<string>","naicsSector":"<string>","keywords":"<string>","excludeKeywords":"<string>","companyKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","emailStatus":"<string>","emailType":"<string>","hasEmail":"<boolean>","hasPhone":"<boolean>","reachable":"<string>","cursor":"<string>","limit":"<integer>","facets":"<boolean>","facetCompanies":"<boolean>","slim":"<boolean>","fields":"<string>","order":"<string>","count":"<boolean>"}}'
```

### People search (JSON)

JSON-body form of GET /v1/people/search: filter people (title, seniority, location, company, industry, email/phone flags and more). Each person returned counts one record; count=true with limit=1 is a free sizing call. Page with meta.nextCursor; 1-100 rows a page (default 25).

`POST /v1/people/search`

**Estimated cost:** Dynamic — use `"dryRun": true` in the Run API request to check the exact cost before calling.

**Page:** https://www.orthogonal.com/api/leadocean/50e4e486-ff86-497a-8620-4eb175fb9050

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over the person: name, title, headline, profile summary, skills, job descriptions, and their company name |
| `profileKeywords` | string | No | the same as keywords — the person’s own profile text; kept under this name for clients that adopted it |
| `excludeProfileKeywords` | string | No | profile keywords to exclude |
| `title` | string | No | job title keywords; wrap a value in [brackets] for an exact match |
| `excludeTitle` | string | No | job titles to exclude |
| `excludeViewed` | boolean | No | leave out the people this account marked viewed (POST /v1/people/viewed) in viewedSet; exact for a list up to 20,000, a skip-ahead walk beyond (see meta.excludedViewed, meta.walkCapped) |
| `viewedSet` | string | No | which viewed list excludeViewed reads, e.g. one per end-client workspace; default "default" |
| `excludeIds` | string | No | person_ids to leave out of the results, e.g. ones you already showed; max 1,000 |
| `seniority` | string | No | LeadOcean seniority band (mapped onto job_level upstream) |
| `jobLevel` | string | No | seniority band as the data source defines it |
| `jobFunction` | string | No | department or function of the current role |
| `country` | string | No | where the person is located |
| `continent` | string | No | continent the person is in |
| `salesRegion` | string | No | commercial region the person is in |
| `city` | string | No | city keywords for the person |
| `excludeCity` | string | No | cities to exclude |
| `education` | string | No | school, degree or year phrases |
| `minConnections` | integer | No | minimum LinkedIn connections, 0–500 — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `domain` | string | No | company domain the person works at |
| `companyName` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeCompanyName` | string | No | company name phrases to exclude; [brackets] for exact |
| `companyLinkedin` | string | No | company LinkedIn URLs |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket; coarser and faster than minEmployees/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minFounded` | integer | No | year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `fundingType` | string | No | type of the last funding round — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `minFunding` | integer | No | total funding raised, USD — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `investors` | string | No | lead investor keywords — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `sic` | string | No | SIC codes of the employer — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `naicsSector` | string | No | two-digit NAICS sector of the employer as STORED on the person record (a SIC crosswalk from the source): the first-listed sector, held for about half of people, as of the last people build — applies directly, never dropped. It can differ from the company record’s derived company_data.naics_sector |
| `keywords` | string | No | keywords in the person’s own profile: headline, summary, skills and job descriptions — the PERSON’s text, not the employer’s (for the company’s text search companies, or filter people by industry / companyName). Each value is a phrase whose words must all appear; several values OR together |
| `excludeKeywords` | string | No | profile keywords to exclude |
| `companyKeywords` | string | No | what the EMPLOYER does, in its own words: each value is a phrase whose words must all appear in the company’s description, specialties, tags or name — or an exact industry label, which then matches every company filed under it; several values OR together. The broad way to ask for "people at cybersecurity companies": an industry label alone misses most of them — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA — matched through the employer: applies when the matching companies (after the HQ, size, industry and company-type filters) number 50,000 or fewer, otherwise named in unsupportedFilters |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | technologies detected on the company website (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `emailStatus` | string | No | email deliverability (own data only) |
| `emailType` | string | No | work or personal email (own data only) |
| `hasEmail` | boolean | No | only people with, or without, a known email (own data only) |
| `hasPhone` | boolean | No | only people with, or without, a known phone number (own data only) |
| `reachable` | string | No | holding an email OR a phone — `strict` additionally requires the email to be verified, catch_all_valid or catch_all |
| `cursor` | string | No | opaque, from meta.nextCursor |
| `limit` | integer | No | records per page, 1–100 (an account enabled for unlimited walks may ask up to 200 on order=stable) |
| `facets` | boolean | No | also return counts by seniority, country, industry and company size |
| `facetCompanies` | boolean | No | also count distinct employers inside each facet bucket (an estimate within ~1%); slower on a wide filter, so off by default — meta.distinctCompanies at the top level comes with every filtered count (null with no filter at all) |
| `slim` | boolean | No | drop empty and heavy parts of each record (picture block, duplicate lists); default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. profile_data.profile_full_name,meta.source_ids; everything else is omitted |
| `order` | string | No | ranked (default): best matches first. stable: every match in id order (person_id / company_id), unscored, on the index snapshot the first page read — for walking a whole result set. Pass order=stable with every page: a stable cursor only continues a stable walk, and a ranked cursor only a ranked search. If the snapshot is retired mid-walk the next page answers 410; start the walk again without a cursor. An account enabled for unlimited walks pages a stable walk to its end, with no depth cap, up |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/people/search","body":{"q":"<string>","profileKeywords":"<string>","excludeProfileKeywords":"<string>","title":"<string>","excludeTitle":"<string>","excludeViewed":"<boolean>","viewedSet":"<string>","excludeIds":"<string>","seniority":"<string>","jobLevel":"<string>","jobFunction":"<string>","country":"<string>","continent":"<string>","salesRegion":"<string>","city":"<string>","excludeCity":"<string>","education":"<string>","minConnections":"<integer>","domain":"<string>","companyName":"<string>","excludeCompanyName":"<string>","companyLinkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","minFollowers":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","sic":"<string>","naicsSector":"<string>","keywords":"<string>","excludeKeywords":"<string>","companyKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","emailStatus":"<string>","emailType":"<string>","hasEmail":"<boolean>","hasPhone":"<boolean>","reachable":"<string>","cursor":"<string>","limit":"<integer>","facets":"<boolean>","facetCompanies":"<boolean>","slim":"<boolean>","fields":"<string>","order":"<string>"}}'
```

### Company enrichment

Look up one company by domain or linkedin_url and get its full company profile. Costs one record.

`GET /v1/companies/enrich`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/eab5a09e-1014-4375-bcdc-b4f89f873f2a

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `domain` | string | No |  |
| `linkedin_url` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/enrich","method":"GET","query":{"domain":"<string>","linkedin_url":"<string>"}}'
```

### Company enrichment (JSON)

JSON-body form of GET /v1/companies/enrich: one company by domain or linkedin_url. Costs one record.

`POST /v1/companies/enrich`

**Estimated cost:** $0.000488

**Page:** https://www.orthogonal.com/api/leadocean/15addcfe-d866-4714-bf9f-4a1499da3b8d

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `domain` | string | No |  |
| `linkedin_url` | string | No |  |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/enrich","body":{"domain":"<string>","linkedin_url":"<string>"}}'
```

### Company search

Each company returned counts one record. Page with meta.nextCursor. One search pages through at most 10,000 rows by default; past that no further cursor is issued and meta.depthCapped is true. The figure is per account — support can raise it for a genuine large export, so ask rather than working around it. It counts rows paged through and is not the monthly records allowance, which is separate. The answer to a capped walk is to narrow the filters and run several smaller searches; paging harder returns no more cursors. A walk of the WHOLE result set is order=stable: id order, on the snapshot the first page read (a 410 means that snapshot was retired mid-walk — start again without a cursor); an account enabled for unlimited walks pages it to its end, up to 200 rows a page, while every other account keeps the depth above and 100 rows.

`GET /v1/companies/search`

**Estimated cost:** Dynamic — use `"dryRun": true` in the Run API request to check the exact cost before calling.

**Page:** https://www.orthogonal.com/api/leadocean/ebc84984-1128-4aa8-96c7-369d724dccc9

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over company name and description |
| `name` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeName` | string | No | company name phrases to exclude; [brackets] for exact |
| `domain` | string | No | company website domains |
| `linkedin` | string | No | company LinkedIn URLs — resolved through the people we hold at the company (most real companies); a URL nobody works at is a 404 pointing at GET /v1/companies/enrich?linkedin_url=…, which always works |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket — broader and cheaper than min/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minRevenue` | integer | No | annual revenue floor in USD — only records whose value we hold; one with no figure on file is never returned |
| `maxRevenue` | integer | No | annual revenue ceiling in USD — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `minFounded` | integer | No | earliest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `fundingType` | string | No | type of the most recent funding round |
| `minFunding` | integer | No | total funding raised, USD floor — only records whose value we hold; one with no figure on file is never returned |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned |
| `investors` | string | No | lead investor name keywords |
| `naics` | string | No | NAICS industry codes — any code the company carries |
| `naicsPrimary` | string | No | the ONE NAICS code a company is filed under (company_data.naics_primary); narrower than naics, which matches any listed code |
| `naicsSector` | string | No | two-digit NAICS sector, DERIVED from the industry label and the codes — the same value the record shows as company_data.naics_sector, so a filtered company always displays the sector it was filtered by. 18 values held; the coarse grouping for sizing |
| `sic` | string | No | SIC industry codes |
| `keywords` | string | No | keywords across company description, specialties, tags and name: each value is a phrase whose words must all appear — or an exact industry label, which then matches every company filed under it; several values OR together |
| `excludeKeywords` | string | No | company keywords (or exact industry labels) to exclude |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | detected technologies (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `hasMailableContacts` | boolean | No | true = companies with at least one person whose best email is verified, catch_all_valid or catch_all; false = companies with none (LeadOcean data only) |
| `cursor` | string | No | Opaque page token: pass back exactly the string meta.nextCursor returned, unchanged. Cursors are signed — one that has been edited, truncated or hand-built is refused with 400 "Invalid cursor", as is one minted for a different search. A cursor is a position in one walk rather than a handle on a result set: do not store it, restart the query instead. Cursors issued before 2026-09-19 no longer verify. |
| `limit` | integer | No | records per page, 1–100 (an account enabled for unlimited walks may ask up to 200 on order=stable) |
| `slim` | boolean | No | drop the technology list (the count stays), tags, specialties, financials and every empty field; default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. company_data.company_name,company_data.company_domain; everything else is omitted |
| `order` | string | No | ranked (default): best matches first. stable: every match in id order (person_id / company_id), unscored, on the index snapshot the first page read — for walking a whole result set. Pass order=stable with every page: a stable cursor only continues a stable walk, and a ranked cursor only a ranked search. If the snapshot is retired mid-walk the next page answers 410; start the walk again without a cursor. An account enabled for unlimited walks pages a stable walk to its end, with no depth cap, up |
| `count` | boolean | No | Also return the exact total number of matches in meta.total. On the PEOPLE search it is opt-in because it is work: a page is ranked either way, a total has to be tallied. The COMPANY search counts its first page regardless and carries the figure in the cursor, so every page of a company walk has meta.total without recounting. FREE WITH limit=1: that combination is a sizing call, costs no records however often you send it, and answers with an empty `data` and `meta.countOnly: true` — the number i |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/search","method":"GET","query":{"q":"<string>","name":"<string>","excludeName":"<string>","domain":"<string>","linkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minRevenue":"<integer>","maxRevenue":"<integer>","minFollowers":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","naics":"<string>","naicsPrimary":"<string>","naicsSector":"<string>","sic":"<string>","keywords":"<string>","excludeKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","hasMailableContacts":"<boolean>","cursor":"<string>","limit":"<integer>","slim":"<boolean>","fields":"<string>","order":"<string>","count":"<boolean>"}}'
```

### Company search (JSON)

JSON-body form of GET /v1/companies/search: filter companies by industry, headcount, revenue, funding, HQ location, technologies and more. Each company returned counts one record. Page with meta.nextCursor; 1-100 rows a page (default 25).

`POST /v1/companies/search`

**Estimated cost:** Dynamic — use `"dryRun": true` in the Run API request to check the exact cost before calling.

**Page:** https://www.orthogonal.com/api/leadocean/49758733-1f83-4580-88ca-2c93818072ad

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over company name and description |
| `name` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeName` | string | No | company name phrases to exclude; [brackets] for exact |
| `domain` | string | No | company website domains |
| `linkedin` | string | No | company LinkedIn URLs — resolved through the people we hold at the company (most real companies); a URL nobody works at is a 404 pointing at GET /v1/companies/enrich?linkedin_url=…, which always works |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket — broader and cheaper than min/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minRevenue` | integer | No | annual revenue floor in USD — only records whose value we hold; one with no figure on file is never returned |
| `maxRevenue` | integer | No | annual revenue ceiling in USD — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `minFounded` | integer | No | earliest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `fundingType` | string | No | type of the most recent funding round |
| `minFunding` | integer | No | total funding raised, USD floor — only records whose value we hold; one with no figure on file is never returned |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned |
| `investors` | string | No | lead investor name keywords |
| `naics` | string | No | NAICS industry codes — any code the company carries |
| `naicsPrimary` | string | No | the ONE NAICS code a company is filed under (company_data.naics_primary); narrower than naics, which matches any listed code |
| `naicsSector` | string | No | two-digit NAICS sector, DERIVED from the industry label and the codes — the same value the record shows as company_data.naics_sector, so a filtered company always displays the sector it was filtered by. 18 values held; the coarse grouping for sizing |
| `sic` | string | No | SIC industry codes |
| `keywords` | string | No | keywords across company description, specialties, tags and name: each value is a phrase whose words must all appear — or an exact industry label, which then matches every company filed under it; several values OR together |
| `excludeKeywords` | string | No | company keywords (or exact industry labels) to exclude |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | detected technologies (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `hasMailableContacts` | boolean | No | true = companies with at least one person whose best email is verified, catch_all_valid or catch_all; false = companies with none (LeadOcean data only) |
| `cursor` | string | No | opaque, from meta.nextCursor |
| `limit` | integer | No | records per page, 1–100 (an account enabled for unlimited walks may ask up to 200 on order=stable) |
| `slim` | boolean | No | drop the technology list (the count stays), tags, specialties, financials and every empty field; default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. company_data.company_name,company_data.company_domain; everything else is omitted |
| `order` | string | No | ranked (default): best matches first. stable: every match in id order (person_id / company_id), unscored, on the index snapshot the first page read — for walking a whole result set. Pass order=stable with every page: a stable cursor only continues a stable walk, and a ranked cursor only a ranked search. If the snapshot is retired mid-walk the next page answers 410; start the walk again without a cursor. An account enabled for unlimited walks pages a stable walk to its end, with no depth cap, up |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/search","body":{"q":"<string>","name":"<string>","excludeName":"<string>","domain":"<string>","linkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minRevenue":"<integer>","maxRevenue":"<integer>","minFollowers":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","naics":"<string>","naicsPrimary":"<string>","naicsSector":"<string>","sic":"<string>","keywords":"<string>","excludeKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","hasMailableContacts":"<boolean>","cursor":"<string>","limit":"<integer>","slim":"<boolean>","fields":"<string>","order":"<string>"}}'
```

### Company count

Market sizing: the exact number of companies matching the same filters /v1/companies/search takes, broken down by industry, headcount band, HQ country, HQ state and NAICS. Costs nothing and returns no rows. No email-status default applies — it counts companies, not mailable people; `hasMailableContacts=true` restricts to companies with at least one person whose best email is verified, catch_all_valid or catch_all.

`GET /v1/companies/count`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/43564df0-de3b-487d-a0f6-1c0606c1f1c7

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over company name and description |
| `name` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeName` | string | No | company name phrases to exclude; [brackets] for exact |
| `domain` | string | No | company website domains |
| `linkedin` | string | No | company LinkedIn URLs — resolved through the people we hold at the company (most real companies); a URL nobody works at is a 404 pointing at GET /v1/companies/enrich?linkedin_url=…, which always works |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket — broader and cheaper than min/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minRevenue` | integer | No | annual revenue floor in USD — only records whose value we hold; one with no figure on file is never returned |
| `maxRevenue` | integer | No | annual revenue ceiling in USD — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `minFounded` | integer | No | earliest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `fundingType` | string | No | type of the most recent funding round |
| `minFunding` | integer | No | total funding raised, USD floor — only records whose value we hold; one with no figure on file is never returned |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned |
| `investors` | string | No | lead investor name keywords |
| `naics` | string | No | NAICS industry codes — any code the company carries |
| `naicsPrimary` | string | No | the ONE NAICS code a company is filed under (company_data.naics_primary); narrower than naics, which matches any listed code |
| `naicsSector` | string | No | two-digit NAICS sector, DERIVED from the industry label and the codes — the same value the record shows as company_data.naics_sector, so a filtered company always displays the sector it was filtered by. 18 values held; the coarse grouping for sizing |
| `sic` | string | No | SIC industry codes |
| `keywords` | string | No | keywords across company description, specialties, tags and name: each value is a phrase whose words must all appear — or an exact industry label, which then matches every company filed under it; several values OR together |
| `excludeKeywords` | string | No | company keywords (or exact industry labels) to exclude |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | detected technologies (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `hasMailableContacts` | boolean | No | true = companies with at least one person whose best email is verified, catch_all_valid or catch_all; false = companies with none (LeadOcean data only) |
| `slim` | boolean | No | drop the technology list (the count stays), tags, specialties, financials and every empty field; default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. company_data.company_name,company_data.company_domain; everything else is omitted |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/count","method":"GET","query":{"q":"<string>","name":"<string>","excludeName":"<string>","domain":"<string>","linkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minRevenue":"<integer>","maxRevenue":"<integer>","minFollowers":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","naics":"<string>","naicsPrimary":"<string>","naicsSector":"<string>","sic":"<string>","keywords":"<string>","excludeKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","hasMailableContacts":"<boolean>","slim":"<boolean>","fields":"<string>"}}'
```

### Company count (JSON)

JSON-body form of GET /v1/companies/count: exact number of companies matching the company-search filters, with breakdowns. Free, returns no rows.

`POST /v1/companies/count`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/16fbfe7d-39f1-43b7-a47c-b1eef4688b72

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `q` | string | No | free text over company name and description |
| `name` | string | No | company name phrase (all words, adjacent); wrap a value in [brackets] for an exact name match |
| `excludeName` | string | No | company name phrases to exclude; [brackets] for exact |
| `domain` | string | No | company website domains |
| `linkedin` | string | No | company LinkedIn URLs — resolved through the people we hold at the company (most real companies); a URL nobody works at is a 404 pointing at GET /v1/companies/enrich?linkedin_url=…, which always works |
| `industry` | string | No | company industry |
| `excludeIndustry` | string | No | industries to exclude |
| `companyType` | string | No | legal type of the company |
| `employeeRange` | string | No | headcount bracket — broader and cheaper than min/maxEmployees |
| `minEmployees` | integer | No | company headcount, lower bound — only records whose value we hold; one with no figure on file is never returned |
| `maxEmployees` | integer | No | company headcount, upper bound — only records whose value we hold; one with no figure on file is never returned |
| `minRevenue` | integer | No | annual revenue floor in USD — only records whose value we hold; one with no figure on file is never returned |
| `maxRevenue` | integer | No | annual revenue ceiling in USD — only records whose value we hold; one with no figure on file is never returned |
| `minFollowers` | integer | No | minimum company LinkedIn followers — 0 means no minimum; any value of 1 or more matches only records whose figure we hold |
| `minFounded` | integer | No | earliest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `maxFounded` | integer | No | latest year the company was founded — only records whose value we hold; one with no figure on file is never returned |
| `fundingType` | string | No | type of the most recent funding round |
| `minFunding` | integer | No | total funding raised, USD floor — only records whose value we hold; one with no figure on file is never returned |
| `maxFunding` | integer | No | total funding raised, USD ceiling — only records whose value we hold; one with no figure on file is never returned |
| `minLastFundingYear` | integer | No | funded no earlier than this year — only records whose value we hold; one with no figure on file is never returned |
| `maxLastFundingYear` | integer | No | funded no later than this year — only records whose value we hold; one with no figure on file is never returned |
| `investors` | string | No | lead investor name keywords |
| `naics` | string | No | NAICS industry codes — any code the company carries |
| `naicsPrimary` | string | No | the ONE NAICS code a company is filed under (company_data.naics_primary); narrower than naics, which matches any listed code |
| `naicsSector` | string | No | two-digit NAICS sector, DERIVED from the industry label and the codes — the same value the record shows as company_data.naics_sector, so a filtered company always displays the sector it was filtered by. 18 values held; the coarse grouping for sizing |
| `sic` | string | No | SIC industry codes |
| `keywords` | string | No | keywords across company description, specialties, tags and name: each value is a phrase whose words must all appear — or an exact industry label, which then matches every company filed under it; several values OR together |
| `excludeKeywords` | string | No | company keywords (or exact industry labels) to exclude |
| `hqCountry` | string | No | company headquarters country |
| `hqCity` | string | No | company headquarters city keywords |
| `hqState` | string | No | company headquarters state or region — a US state, Canadian province, Australian state or German Land also matches its other spellings ("TX" finds "Texas", "Bayern" finds "Bavaria"), at companies in that country only; add hqCountry to pin an ambiguous code such as WA |
| `hqContinent` | string | No | continent of the company headquarters |
| `hqSalesRegion` | string | No | commercial region of the company headquarters |
| `technologies` | string | No | detected technologies (own data only) |
| `technologyCategories` | string | No | what the detected technology is for, e.g. Analytics or CDN, rather than its name (own data only; covers the ~7.8M crawled companies) |
| `hasMailableContacts` | boolean | No | true = companies with at least one person whose best email is verified, catch_all_valid or catch_all; false = companies with none (LeadOcean data only) |
| `slim` | boolean | No | drop the technology list (the count stays), tags, specialties, financials and every empty field; default false over REST, true over MCP |
| `fields` | string | No | dotted paths to keep, e.g. company_data.company_name,company_data.company_domain; everything else is omitted |

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/count","body":{"q":"<string>","name":"<string>","excludeName":"<string>","domain":"<string>","linkedin":"<string>","industry":"<string>","excludeIndustry":"<string>","companyType":"<string>","employeeRange":"<string>","minEmployees":"<integer>","maxEmployees":"<integer>","minRevenue":"<integer>","maxRevenue":"<integer>","minFollowers":"<integer>","minFounded":"<integer>","maxFounded":"<integer>","fundingType":"<string>","minFunding":"<integer>","maxFunding":"<integer>","minLastFundingYear":"<integer>","maxLastFundingYear":"<integer>","investors":"<string>","naics":"<string>","naicsPrimary":"<string>","naicsSector":"<string>","sic":"<string>","keywords":"<string>","excludeKeywords":"<string>","hqCountry":"<string>","hqCity":"<string>","hqState":"<string>","hqContinent":"<string>","hqSalesRegion":"<string>","technologies":"<string>","technologyCategories":"<string>","hasMailableContacts":"<boolean>","slim":"<boolean>","fields":"<string>"}}'
```

### Company employee list

Thin records, one record billed per person returned. Contact points are not included — enrich a person for those. Page with the cursor from meta.nextCursor. BEHAVIOUR CHANGE, 2026-09-19: this roster is now subject to the same depth cap and the same signed cursors as search, where before it paged without any limit and passed its cursor through unsigned. A roster deeper than the cap stops issuing cursors, with meta.depthCapped true on the last page, and a cursor issued before that date is refused with 400 "Invalid cursor" — restart the walk. Rosters are bounded by company size, so almost none reach the cap. One search pages through at most 10,000 rows by default; past that no further cursor is issued and meta.depthCapped is true. The figure is per account — support can raise it for a genuine large export, so ask rather than working around it. It counts rows paged through and is not the monthly records allowance, which is separate. The answer to a capped walk is to narrow the filters and

`GET /v1/companies/{domain}/people`

**Estimated cost:** Dynamic — use `"dryRun": true` in the Run API request to check the exact cost before calling.

**Page:** https://www.orthogonal.com/api/leadocean/93a2f96a-b889-46be-8ea9-42b95b230134

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `domain` | string | Yes | Path parameter — substitute directly into the endpoint `path`. |
| `cursor` | string | No | Opaque page token: pass back exactly the string meta.nextCursor returned, unchanged. Cursors are signed — one that has been edited, truncated or hand-built is refused with 400 "Invalid cursor", as is one minted for a different search. A cursor is a position in one walk rather than a handle on a result set: do not store it, restart the query instead. Cursors issued before 2026-09-19 no longer verify. |
| `limit` | integer | No |  |

```bash
# Replace {domain} in "path" with real values before sending
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/companies/{domain}/people","method":"GET","query":{"cursor":"<string>","limit":"<integer>"}}'
```

### People search filters

The people-search filter contract: every filter, its type and allowed values source. Free to read.

`GET /v1/filters/people`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/779ed3a8-6762-4a9e-8753-4339d1c0e471

**Docs:** https://leadocean.io/docs

_No parameters required._

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/filters/people","method":"GET"}'
```

### Company search filters

The company-search filter contract: every filter, its type and allowed values source. Free to read.

`GET /v1/filters/companies`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/711ee8d9-750b-47db-8963-945a18d11686

**Docs:** https://leadocean.io/docs

_No parameters required._

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/filters/companies","method":"GET"}'
```

### Filter index

Index of all search filters, the enum catalogue and schema names. Free to read.

`GET /v1/filters`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/33673b7c-efb8-46e7-8c93-6cedcf8a1699

**Docs:** https://leadocean.io/docs

_No parameters required._

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/filters","method":"GET"}'
```

### Enum catalogue

Every enum (industries, seniorities, countries and more) with its size and the filters it applies to. Free to read.

`GET /v1/enums`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/5855f097-717f-4abf-846e-588d9cebcc39

**Docs:** https://leadocean.io/docs

_No parameters required._

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/enums","method":"GET"}'
```

### Enum values

The values of one enum, searchable with q. Free to read.

`GET /v1/enums/{name}`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/685ca691-3604-49d6-b380-750378ab8328

**Docs:** https://leadocean.io/docs

| Field | Type | Required | Description |
|-------|------|----------|-------------|
| `name` | string | Yes | Path parameter — substitute directly into the endpoint `path`. |
| `q` | string | No | Filter values by substring — how you find the exact string for a concept |
| `limit` | integer | No |  |

```bash
# Replace {name} in "path" with real values before sending
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/v1/enums/{name}","method":"GET","query":{"q":"<string>","limit":"<integer>"}}'
```

### Dataset coverage

People, and how many of them carry a work email (a `work` or `work_other` address), a personal email and a phone number, for the whole index and for every country grouped into the four sales regions (NORAM, EMEA, APAC, LATAM; Antarctica, the uninhabited territories and people with no country under Other). Free, no key, no record. Computed at most once a day — read computedAt. Percentages are yours to take: fill.work / people. 202 with data null only before the first computation has landed.

`GET /coverage`

**Cost:** Free

**Page:** https://www.orthogonal.com/api/leadocean/f114bfa3-e420-4a2c-b4fa-a5d0e1e82b53

**Docs:** https://leadocean.io/docs

_No parameters required._

```bash
curl -X POST 'https://api.orthogonal.com/v1/run' \
  -H 'Authorization: Bearer $ORTHOGONAL_API_KEY' \
  -H 'Content-Type: application/json' \
  -d '{"api":"leadocean","path":"/coverage","method":"GET"}'
```

---

Full details and an interactive quickstart: https://www.orthogonal.com/publisher/leadocean
