Skip to main content
Your organization shares one credit balance across its API keys and managed workloads. Read key_metadata.credits_consumed and credits_remaining in JSON responses; X-Credits-Used reports request usage in the response headers.

​
Operation prices

​
Scrape modifiers

The base applies when at least one output succeeds, including cache hits. If every output fails, no charge applies, except when the target is missing: a target 404 retains the base charge, plus 1 when product was requested.

​
When requests are charged

Successful and partial results are charged. Processed 404s on priced data APIs are charged at their applicable price. Validation, authentication, permission, 408, 429, and server errors are not. Brand 400 NOT_FOUND and People not_found are not charged. Tags and ZDR do not change prices. Batches reserve credits at submission for accepted URLs, or the crawl’s maxUrls ceiling. Unsuccessful or unused pages are refunded when the batch settles; OCR is added then. See credits.reserved, refunded, ocr_charged, and net on the batch.

​
Free balance and refills

Work-email Free organizations receive 1,000 credits monthly on their grant-anchor day. Personal-email Free organizations receive 250 once, without refills. Only one unpaid organization is allowed per person. Extra grants above the Free allowance are preserved at refill. Paid balances reset to the monthly allowance after a paid refill; unused credits normally do not roll over. See plans and billing for upgrades, pauses, and the exception for remaining balance during an upgrade. Use Earn free credits or Redeem a code in the dashboard when available. Paid plans can enable Auto-Topup. Dollar prices and Logo Link allowances are on the pricing page.