Credits & billing

Every endpoint costs a fixed number of credits per successful request. You can fund credits with a subscription, a one-off purchase, or both.

Where credits come from

• Monthly allowance from a subscription. Resets at each renewal and does not roll over.
• Pay-as-you-go credits bought in packs. They never expire.

Order of spending

The monthly allowance is used first, then pay-as-you-go credits. A request that needs more credits than are available is rejected with 402 insufficient_credits, and nothing is charged.

When you are charged

Credits are deducted only when a request succeeds. These outcomes are never charged:

• 400 invalid or missing parameters (rejected before reaching the data provider)
• 404 no data found for the lookup
• 502 / 504 data provider errors and timeouts
• 401, 402, 429 authentication, balance and rate-limit rejections

Tracking usage

Each response carries x-credits-charged and x-credits-remaining. The console shows per-day usage, a per-endpoint breakdown and a searchable request log with request IDs.

See pricing for plan and pack details.