Skip to main content
CompanyEnrich bills in credits. Paid endpoints deduct credits for the data they return, and many endpoints are free. As a rule, you pay for results, not for requests: a lookup that finds nothing is usually not charged. The prices on this page are for the V2 API. V1 prices differ in a few places. Each endpoint’s page in the API reference states its own price.

V2 prices

Companies

People

People search costs 2 credits per person in every mode, including semantic queries and company queries.

Free endpoints

These endpoints never deduct credits:

Expansions

The expand parameter adds paid data to a record. Expansions are charged on top of the base price, and only for records that are returned. Details worth knowing:
  • Repeating an expansion in the same request does not multiply its cost.
  • The workforce expansion includes the latest 12 months of history. Each earlier 12-month page from GET /v2/companies/workforce costs another credit.
  • The person company expansion adds full company profiles to a person’s current and past experiences. In a search it is charged once per unique company on each response page, even when several people share an employer. The same company on a later page or in another request is charged again.
  • A people search page can expand at most 500 unique companies. A page over that limit returns 400 before anything is charged. Reduce pageSize or remove company from expand.

When you are not charged

There are two exceptions to “no result, no charge”:
A search that returns no results costs one result’s base price: 1 credit for a filter search, 2 for a semantic search, 5 for a lookalike search, and 2 for a people search. Use the free count endpoints to check a query first.POST /v2/companies/enrich costs 1 credit when a company is returned and also when the properties you sent cannot be resolved to a company domain.

Worked examples

Bulk jobs and exports

Background jobs use the same prices as the equivalent synchronous calls.
  • Bulk enrichment (POST /v2/companies/enrich/bulk) checks your balance when you create the job. It returns 402 unless your balance covers every domain at the enrichment price plus the expansions you asked for. Credits are not reserved, and you are charged as results complete.
  • Search exports (companies and people) run as a series of ordinary search pages. There is no upfront balance check. If your credits run out partway, the export stops and the records already exported stay downloadable.
  • Cancelling a batch stops the remaining work. Results that were already charged stay downloadable.

Estimate before you spend

1

Count the matches

The count endpoints take the same query as a search and return how many records match, for free.
2

Preview a sample

If your plan includes previews, the preview endpoints return a small sample of summaries for free, so you can check that a query finds the right kind of record.
3

Set the page size to what you need

Search is charged for every record on a page you fetch, even if you only use the first few. Set pageSize close to the number of results you plan to use.
The CLI adds a --dry-run flag that prints a credit estimate without sending the request, and asks for confirmation before large spends.

Track your balance

API responses include headers that show what a request cost: To check your balance without spending anything, call the free current-user endpoint. It returns your credits and the capabilities of your plan.
You can also see your balance and manage your plan in the dashboard.

When you run out

If your balance cannot cover a paid request, the API returns 402 Payment Required. The official SDKs raise a dedicated error for this response, such as PaymentRequiredError in the Python and Ruby SDKs and PaymentRequiredException in the PHP SDK. The CLI exits with code 5. A 402 can also mean your plan does not include the feature you requested, so check the response’s detail field.

V1 prices

The V1 API uses the same credits and the same headers. Most prices match V2, with a few differences. Empty search results are charged the same way in both versions. Check the endpoint’s page in the V1 reference before relying on a V1 price.