Skip to content

Credit

published · September 10, 2026 · updated · October 2, 2026

A credit is the billing unit of the whole API: one credit buys one fresh lookup that produced a usable answer on any of the six signals, or five on IP.

A credit is the billing unit of the whole API: one credit buys one fresh lookup that produced a usable answer, on any of the six signals, except IP, where one credit buys five. There is one balance and it does not care which endpoint spends it.

On IP the credit is spent in a block: the answered lookup that opens a block shows credits_used 1 and leaves four lookups prepaid on the account, the next four show credits_used 0, and meta.ip_lookups_prepaid says how many are left.

What does not cost one

Three things, and they are the reason the rate card exists rather than a single sentence.

A non-answer is free. What counts as one differs by signal and is published per signal on the pricing page: an invalid phone number, an unparseable postal address, an identifier no installed register carries, an email address with no working mail server. A rejected request is free — a validation error, a refused key, a rate limit. And a repeat of the same value inside seven days is free, held as a keyed marker that stores a hash rather than the value.

An email answer whose mailbox check could not settle — reason unverified, whether the receiving server would not say or the partner infrastructure behind the handshake was down — is also free, because nothing was established. An undeliverable email verdict that needed a mailbox check is free within a fair-use allowance and costs a credit past it, with meta.fair_use_billed saying so.

When there are none left

The API answers 402 INSUFFICIENT_CREDITS before running the lookup, so an empty balance never bills for work that could not complete. Free credits renew at the start of each month and pack credits never expire. Plan credits roll over up to three months' allowance and stay usable for 60 days after you cancel.

meta.credits_used on every response says what that call actually cost, including zero.

Related

markdown version: /glossary/credit.md

Verify addresses the same way

The Spaw API runs every check described here on each lookup, with an SMTP handshake that never sends mail. 10 free lookups a month, no card required.

Get your API key

More glossary

  • Area-code overlay

    An area-code overlay is a new area code added over the same area as an existing one, instead of splitting it, so neighbours can hold different codes and local calls need ten digits.

  • Calling window

    A calling window is the span of local hours a sender contacts people in. Spaw answers in_call_window from the number's time zones: clock arithmetic, not compliance advice.

  • Fictional number

    A fictional number sits in a range kept out of service for films, TV and other fiction: 555-0100 to 555-0199 in North America, and ranges Ofcom, ARCEP, ACMA and ComReg reserve elsewhere.

  • International (exit) prefix

    An international prefix is what is dialled to leave a country before the calling code: 00 in most of the world, 011 in North America. Spaw reads it and suggests a fix in did_you_mean.

  • International network number

    An international network number sits under a calling code the ITU gives a global service rather than a country, such as +870, +881, +882 or +883, so its country is null.

  • Live carrier check (HLR lookup)

    A live carrier check asks the mobile networks, at the moment of the lookup, whether a number is in service, which network serves it and whether it is roaming. On Spaw it is not enabled.

  • Number pooling (thousands-blocks)

    Number pooling splits a North American central office code into ten blocks of a thousand numbers, each assigned to a carrier separately, so one code can hold several carriers' numbers.

  • Number portability

    Number portability lets a subscriber keep a phone number when changing carrier. The number's block stays listed under the carrier it was issued to, so block data names the original holder.