Skip to main content
Every organization is on a plan with a monthly balance of credits, and every request spends credits according to what it costs to serve: Plans start free, with no card. What each plan includes and what it costs is on the pricing page.

​
What spends nothing

  • A cached answer (X-Cache: HIT, or cache_hit: true on a batch item), though the request still needs enough credits to be accepted.
  • A failed request.
  • Polling a job’s status.
Batch requests spend credits per item: a batch of 10 live lookups spends 100.

​
Your balance on every response

Three headers carry the balance. X-RateLimit-Limit is the credits your plan grants each month, X-RateLimit-Remaining is what is left after this request, and X-RateLimit-Reset is when the balance refills:
The balance resets on the plan’s monthly date. Manage the plan from the console. Contracts carry their own monthly number.

​
When the credits are spent

A request your remaining credits cannot cover returns 402 with a billing_error envelope. Upgrade from the console, or wait for the reset in X-RateLimit-Reset:

Next: Rate limits

The hourly ceilings on a few endpoints, every header and how 429 behaves.