Every API call is one request, and each request containing one lookup spends exactly one credit, whatever data it returns.
Batch requests using our batch endpoints are the only exception:
one credit per lookup in the batch request, plus 1 for the batch request call itself.
Credits are bought in two self-serve ways, and each purchase fills its own balance. Enterprise agreements can add a third balance on top: overage that keeps requests flowing.
A monthly credit allowance at the lowest cost per credit, renewed every month.
Fills your subscription credits balanceBuy once, use anytime. Pack credits never expire and need no subscription.
Fills your pack credits balanceA committed monthly allowance on custom terms, with optional overage so requests keep being served.
Adds the overage balanceEvery request draws down your subscription credits first, then your packs, then Enterprise overage. Nothing is wasted and nothing expires early.
If you're on a plan, its monthly allowance is always spent first. It renews every month, yearly plans included, and any unused balance does not roll over.
One-time credit packs are spent only once your subscription (if any) runs out for the period. Pack credits never expire and need no subscription at all, so they work standalone too.
The Enterprise plan supports overage. When it is enabled for your account, requests keep working once every other balance is exhausted and are billed at the agreed rate. Without it, requests are refused until the allowance is renewed.