API credits
Usage is measured in lookups. Understanding how lookups are counted keeps your bill predictable.
How lookups work
- 1 fresh lookup = 1 credit. Each query that hits the source registry counts as one lookup.
- Cached lookups are free. Repeat the same query within your cache window and it won’t be billed again.
- Monthly reset. Plan lookups reset at the start of each billing cycle. One-time credit packs never expire.
- Overage billing. On paid plans, lookups beyond your included volume bill at your plan’s per-lookup rate.
What costs a credit
| Action | Credits | Notes |
|---|---|---|
| Entity search (fresh) | 1 | Counted once per unique query — by name or by registry ID |
| Entity search (cached) | 0 | Served from cache within your window |
| Name availability check | 1 | One live registry lookup per check |
| Bulk search | 1 per row | Each searched name costs one lookup, found or not — a 100-row file uses up to 100 credits |
| MCP: search_business_entity | 1 | Metered exactly like a REST call |
| MCP: all other tools | 0 | Listing states, managing monitors, and reading the change feed are free |
| Monitor: scheduled re-checks | 0 | Monitors are sold as plan slots — the scheduled checks don’t draw from your credits |
| Monitor: manual “Check now” | 1 | An on-demand re-check runs one live lookup |
| UCC search (beta) | 1 | Same per-lookup model |
One caveat: metering happens when your key is validated, so a request that then fails — a typo’d parameter, an unsupported state — still consumes its credit. Validate inputs on your side (or against list_supported_states) before sending.
Need more volume? Compare plans and one-time credit packs on the pricing page.
Monitoring usage
Track lookups, error rate, and latency in real time from the Usage tab of your dashboard. Set up alerts to know before you hit your limit.