Skip to main content
Compare API usage on Pay-as-you-go (PAYG) and All-you-can-eat (AYCE). AYCE includes unlimited contact and company retrieval, including available contact email and mobile details. Email Verification has its own per-result prices below. Per-request, masked-sample, and rate limits still apply on both plans.

​
Compare contact endpoint costs

View returns up to 100 rows per request and has a 100,000-row daily sample budget per API key on either plan. On AYCE, use Preview or Export for full records; View’s sample allowance does not limit your included contact retrieval. 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:
Contact Preview uses the same chart on PAYG. Contact Enrich charges matching rows and selected populated details; it has no search-filter tree or SmartSearch fee. Company enrichment costs 1 per returned company; company exports add any SmartSearch filter-node charges to the company-row amount. Missing selected email/mobile values add no detail charge. An empty ordinary retrieval has no row charge, but a successful empty paid search/export with SmartSearch nodes can still charge the flat SmartSearch amount.

​
Choose contact details explicitly

Omitting reveal, or sending null, selects both email and mobile. Choosing fewer columns does not remove reveal charges. Set reveal explicitly on paid contact requests.
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

With maxRows: 100 and email selected, the hold is up to 200 credits. With both details and one SmartSearch node, it is up to 1,210 credits, even when the final charge is the 390-credit example above. 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. Always use a positive row cap; 0 uses the maximum. 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

Preview and Enrich reserve a PAYG hold before retrieving records. Preview uses the applied limit; 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 holds against the row cap plus SmartSearch 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 as REVENUEBASE_API_KEY.
Use the free price catalog when your application calculates a retrieval bound:
Price response for the chart above:
Metered synchronous retrieval responses expose 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.

​
Repeat requests and downloads

Repeated paid retrievals and new export POSTs can charge again, including for the same records. Do not automatically repeat a start POST after an ambiguous timeout. If you have an export ID, poll that job instead. Polling an existing export, refreshing its signed link, and downloading the same completed file again do not start another paid export. Follow the export recovery guidance.

​
Next steps