How Ipregistry Credits Work

Credits and balances, spent in a predictable order.

What is a credit?

1 lookup= 1 request= 1 credit

Every API call is one request, and each request containing one lookup spends exactly one credit, whatever data it returns.

Batch request of 3 lookups = 3 + 1 credits

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.

Getting credits

Where credits come from

Credits are bought in two self-serve ways, and each purchase fills its own balance. Enterprise agreements add a third balance on top: overage that keeps requests flowing.

How credits work

Three balances, always spent in the same order

Every request draws down your subscription credits first, then your packs, then Enterprise overage. Nothing is wasted and nothing expires early.

1. Subscription credits

If you're on a plan, its monthly allowance is always spent first. It renews every billing cycle and any unused balance does not roll over.

2. Pack credits

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.

3. Overage

Enterprise plan supports overage. Once every other balance is exhausted, requests keep working and are billed automatically instead of being blocked. Optional, and never a hard stop.

See plans and pricing