Search first
Use search endpoints for low-cost discovery, then enrich only the
records you want to keep.
Enrich selectively
Person enrich starts with a base profile and adds cost only when you ask
for higher-value data.
Plan for live endpoint usage
Web live endpoints are available on self-serve plans. Company and Person
live endpoints remain plan-gated.
Self-serve endpoint pricing
This page lists pricing for the endpoints currently documented in this docs
site. It does not include unpublished or not-yet-documented routes.
X-Credits-Used response header
returned on every request.
Your account’s own prices
The tables below are standard list prices. If your account is on a negotiated or contract rate, the prices you pay are returned byGET /account/endpoints — one free call, no credits,
every endpoint with its base_credits and any per-field or per-flag extras
priced for your account. It is the authoritative answer to “what does this
cost me”, and a cost estimator can read it directly:
premium_filters, premium_fields, and premium_modes.
You can also see your prices in the dashboard.
The “Your price” column in each endpoint table below links to the Pricing
tab of that endpoint. The tab shows the prices for your account.
- The link works only for an endpoint enabled for your account. For any other endpoint, the dashboard opens your endpoint list.
- A batch endpoint links to the tab of its non-batch endpoint, because batch
costs the same. For example,
/batch/person/searchlinks to the tab of/person/search. - A free endpoint has no link.
- A watcher row links to the dashboard watch builder instead, because
/account/endpointsdoes not carry watch prices. The link opens the builder on that watcher and that SLA. The screen quotes your price per record. The 3-day tier has no link, because the builder does not offer it.
Premium fields in search
Search charges a base price per result, plus a per-field price for premium fields. The two sides are billed independently: filtering on a premium field is one charge, receiving it in the response is another, and sorting on one is free. Both are per result. A request that touches no premium field pays the base price alone. A premium group you request that comes backnull, because the record has no
data for it, is not billed.
Prices below are standard list prices; call
/account/endpoints for the prices on your account,
and for which of these fields your plan can use today.
Person search
A group is one charge however many of its members you touch: languages rides
professional network, recently changed jobs rides experience. Summary is
response-only, and the dev platform groups are filter-only — search never
returns them, so only the filter side bills. A result that touches every
returnable premium field costs 2.03 credits, or 2.43 with research
profiles; the GitHub units add 0.8 (basic) or 2.5 (repositories) per
result on the filter side. Research profiles are enabled per account, see
Research profiles.
Company search
Technographics is filter-only — search never returns it, so only the filter
side bills. More company groups (market intel, SEO, web traffic, news,
employee reviews, people) are on the way; they will appear here and in
/account/endpoints as they become available.
Person endpoints
Company endpoints
Job endpoints
Web endpoints
Social Post endpoints
Agent Search endpoints (beta)
Agent Search charges each search once, by the first read or stream that sees it end. The charge grows with the effort of the search, in credits. It has four parts, and the search shows them incredits_used.
The price of each part is rounded up to the next 0.01 credit, so every part
and the total have at most 2 decimal places. A search that finds nothing,
fails, or is cancelled costs 0.
Balance needed to start
A start checks that your balance covers 8 credits for each search of your account that has no charge yet, the new one included. A search has no charge yet while it runs, and after it ends until someone reads it. The check takes no credits, and 8 credits is not the price of a search: a search usually costs much less. See Balance needed to start.Watcher endpoints
Every watcher is priced by its SLA: how fresh the data behind a notification is kept, written asconfig.refresh_frequency_days. A 1-day SLA refreshes daily, which is the level a realtime watch runs at.
How you ask for a 1-day SLA depends on the watcher. A discovery watch takes
config.is_realtime: true, which searches the web live on each run rather than reading the index; the key is what puts the watch on the 1-day SLA, and the create response echoes config.refresh_frequency_days: 1. A person entity watch takes config.refresh_frequency_days: 1 directly. Either way the rate is the same 150 credits per delivered record.
A 1-day SLA discovery watch runs once a day at most, so config.trigger.every_hours must be 24 or more. The filter fields each dataset’s live search accepts are on its own watcher page: Person, Company, Job, Social Post.
You’re charged only for what’s delivered on recurring runs. A discovery run that finds nothing new, or an entity run where nothing changed, costs nothing. Each watcher lives under its dataset. Person and Company each have an Entity and a Discovery watcher; Job and Social Post have a Discovery watcher only.
A person entity watcher has three SLA tiers between the two ends of the table above. The rate is tiered by config.refresh_frequency_days and does not depend on how often the watch runs.
Company entity watchers run at the 30-day SLA only (5 credits per changed company).
Batch endpoint
Person enrich pricing
Person enrich uses additive pricing. You pay for the base profile first, then add credits only for the extra data you request.
The maximum current cost for a single enriched person record is 9 credits.
The base credit is charged once per matched record.
Common credit patterns
Person Contact pricing
/person/contact/enrich bills per requested
contact type, per matched person — there is no base credit (the endpoint
returns contact data only).
Only the types you request are fetched and billed. Omitting
fields requests
all three (5 per matched person, the maximum without verified).
contact.phone_numbers_info belongs to the phone tier and bills the same 2
once, with or without contact.phone_numbers.
contact.websites is not one of the billed contact types, so requesting it
currently uses 0 credits. Identifiers with no match are not billed.
Set verified: true to return only business emails that pass a deliverability
check at request time. Each matched person who receives at least one verified
business email costs 0.5 more, so business emails alone cost 1.5 and
all three types cost 5.5. You pay nothing for the add-on on a person whose
verified list comes back empty. See Verified business emails
only.
/batch/person/contact/enrich bills the same
per-type prices and the same verified add-on, per matched person (maximum
5.5), counted per type, not per record (four business-email candidates
count once).
Person enrich request examples
Use these examples to enrich by profile URL, request specific fields, or reverse-lookup a person from a business email.For full request patterns and field selection behavior, see Person
enrichment.
Enterprise-only and plan-gated live endpoint pricing
Company and Person live endpoints are plan-gated and can have custom quotas or contract pricing.Web Search and Web Fetch are available on self-serve plans. The live Company
and Person endpoints below still require the right plan or enterprise
access.
Live people, company, and job data
Shared live-search endpoints
Free endpoints
These endpoints do not currently consume credits:/person/search/autocomplete/company/search/autocomplete/company/identify/professional_network/search/autocomplete(when enabled for your enterprise plan)POST /agent/searches/{search_id}/cancel
Search vs enrich
Estimate usage before you launch
1
List the endpoints your workflow will call
Separate self-serve, enterprise live, and utility requests. They are not
billed in the same way.
2
Estimate returned records per request
Search pricing depends on results returned, not only the number of
calls.
3
Account for optional data and live modes
Contact data, developer platform data, and enterprise live workflows can
raise per-record cost.
4
Multiply by daily volume
Model normal traffic first, then add weekly or monthly growth
assumptions.
5
Add a buffer for retries and spikes
Keep headroom for queue bursts, replay jobs, and production debugging.
Rate limit considerations
Default rate limits vary by endpoint, ranging from 6 requests per minute onPOST /agent/searches to 300 requests per minute on autocomplete endpoints. See Rate limits for the full per-endpoint table.
For throughput planning, see Rate limits.
Buying credits
The credits page in the dashboard sells credits two ways: a one-time purchase (pick a package, check out through Stripe) and auto top-up (a standing rule that buys a reload automatically when your balance drops below a threshold you set). Both use the same packages and the same pricing. See Auto top-up for how the automatic option works, when you are charged, and the controls that keep it in check.Frequently asked questions
How is search billed?
How is search billed?
Search is billed per result returned. For example, 10 results at
0.03
credits per result use 0.30 credits. A request that returns no results
uses no credits. A premium group adds its per-result price on top
when you filter on it, and again when you receive it, see
Premium fields in search.How do I keep person enrich costs under control?
How do I keep person enrich costs under control?
Start with the base profile. Add business email, personal email, phone,
or developer platform data only when your workflow uses it.
What happens when I run out of credits?
What happens when I run out of credits?
Billable requests return an error until you purchase more credits or
your account is replenished under your plan. To avoid interruptions,
turn on auto top-up.
Do unused credits expire?
Do unused credits expire?
Yes. Purchased credits expire 12 months after the purchase that added
them. Credits granted by your account manager may carry a custom
expiry. See Credit expiry.

