Compare contact endpoint costs
View returns up to 100 masked contact rows per request.
PAYG has a shared allowance of 5,000 free preview rows per organization per UTC day across Contact View, Company View, and Company Preview. All members and API keys share it. Each returned row counts, including repeated previews; empty and failed queries do not. SmartSearch adds no credit charge on these free previews. The allowance resets at 00:00 UTC. AYCE has no daily preview allowance; per-request limits still apply.
On PAYG, all three routes report
X-FreePreview-Remaining. Company View and
PAYG Company Preview also report X-Credits-Charged: 0.
A request near the boundary returns only the remaining allowance with a warning.
At exhaustion, these endpoints return 429 FREE_PREVIEW_CAP_REACHED until UTC midnight.
For paid retrieval, explicitly call a paid endpoint. If the allowance cannot be
checked, the preview endpoints return 503 FREE_PREVIEW_UNAVAILABLE.
Counts are free and do not consume this allowance. Contact Preview (/preview),
reveals, company enrichment, standalone lookalike, and exports retain their
separate paid pricing.
Insights, column metadata, dataset stats, match presets, and credit-price
discovery also cost 0 credits. Reading or cancelling an existing export adds
no credit charge.
Compare retrieval prices
PAYG prices are additive. A SmartSearch node means each semantic or lookalike
node in the filter; its fee is per request, rather than per returned row.
A contact row already contains its available company fields. Requesting those
fields does not add a separate company-row charge.
For contact exports, the final charge is:
Choose contact details explicitly
On PAYG, an email/mobile column requested without its corresponding
reveal
selection becomes a hasEmail / hasMobile availability boolean. On AYCE
Preview and Enrich, columns controls returned fields and reveal does not
mask them.
For example, an email-only file with 100 contacts and 80 populated emails costs
180 credits without SmartSearch: 100 + 80. A file with those same
contacts, both details selected, 20 populated mobiles, and one SmartSearch
node costs 390 credits: 100 + 80 + (20 × 10) + 10.
Distinguish the estimate, hold, and charge
When the whole audience fits within the cap, pricing uses its actual counts.
For the 100-contact example above, the reserve is 180 credits with email only
and 390 credits with both details and one SmartSearch node. If the row cap
cuts the audience, the contact estimate uses a conservative bound based on
how many matching rows have each selected detail.
Your balance must cover the hold. If it cannot, Export returns
402 INSUFFICIENT_CREDITS without starting a job. It does not automatically
export a smaller affordable subset. Reduce maxRows or your reveal choices,
then estimate again. Set a positive integer to cap the export. Omit maxRows
or send null to use the service maximum. Sending 0 returns 422 INVALID_REQUEST.
An unfinished failed or cancelled export releases its hold when it ends.
Cancelling a completed export does not refund it. Completion settles the charge
whether or not you subsequently download the file.
Holds for immediate retrieval
Contact Preview and Enrich reserve a PAYG hold before retrieving records. Preview uses the appliedlimit; Enrich uses the submitted array-entry count before
normalization or duplicate removal. Both assume every requested row or entry
has every selected detail. Their final charge uses the records actually
returned. Unmatched Enrich inputs add no row charge. See the
Preview hold and
Enrich hold
examples before sending a paid request.
Compare company endpoint costs
Company Enrich holds one credit per submitted array entry before deduplication,
then settles against returned matches. Company Export reserves 1 credit per
matching company up to the row cap, plus 10 per SmartSearch node, and settles
against the rows written and node fees. Company fields do not add contact email
or mobile reveal surcharges.
Compare email verification costs
The final verification charge is the number of Valid results plus Invalid
results. Requesting metadata does not change that amount. A batch still needs
enough available credits for its input before it starts. Cancelling a running
batch does not refund already processed Valid or Invalid checks.
See verification statuses and metadata
and the batch workflow.
Check your balance and current prices
Set your API key asREVENUEBASE_API_KEY.
X-Credits-Charged and
X-Credits-Remaining. Export creation instead exposes X-Credits-Held.
The current export status body does not report its final charged-credit amount.
