Free
no card$0/mo
2,500 credits · ~1,250 screens
Build against it. Evaluate it properly — not enough to run a business on.
§00
Priced by volume. Nothing else.
One usage-based model, metered in credits. Every plan sees every dataset and screens with the same engine — plans differ in how much you can spend, and in nothing else.
§01
Developer
monthly$49/mo
75,000 credits · $0.65 per 1,000
The working plan. Roughly 37,500 screens a month, at 120 requests a minute.
Scale
lowest rate$249/mo
500,000 credits · $0.50 per 1,000 — 24% below Developer
Production agent workloads, at 600 requests a minute — the lowest rate we publish.
Prices exclude applicable taxes.
Enterprise
contract · negotiated volume
Negotiated volume, self-hosted or bring-your-own-licence deployment, and terms your auditors can read. Same datasets, same engine, same provenance — that never changes with the contract.
talk to us →§02
Your bill does not disclose your results.
Every operation declares its weight in advance. A search that matches nothing costs exactly what a search matching fifty costs. That is deliberate: a price that moved with what came back would make your invoice an existence oracle — a way to read our answers out of your own billing statement. Every comparable vendor prices per screened entity. We cannot, and would not.
priced per screened entity
- 3,000 names submitted
- —
- billable matches
- 17
- invoice
- $1,700.00
The invoice states how many of your counterparties are designated. Anyone who can read it — finance, an auditor, an attacker — can binary-search the list by watching the bill.
priced per declared weight
- 3,000 screens × 2 credits
- 6,000
- billable matches
- not a field
- invoice
- $3.90
The same bill arrives whether every name cleared or none did. The number of hits is not represented anywhere in it, because it never enters the meter.
§03
What a credit is.
A credit is one unit of the weight an operation declares. The weight is fixed before the operation runs and never depends on what it returns.
operation
credits
read — get an entity, a country, a code
1
search / screen
2
uncached release diff
50
the full weight table and how the meter works → /docs#limits
on the free plan
2,500 credits is enough to build against and evaluate properly, not enough to run a business on. That is the whole of the limit — the data and the matcher are the same ones a paid plan gets.
§04
Questions.
- What happens when I run out?
- Requests return 429 until the period resets, or immediately if you upgrade. Your keys stay valid — nothing is revoked and nothing is deleted.
- Do credits roll over?
- No. On a paid plan the allowance resets on your subscription's renewal date each month; on Free it resets on the first of each calendar month (UTC). Unused credits do not carry forward.
- Can I change plans mid-month?
- Yes. An upgrade takes effect immediately: Stripe prorates the charge and the new plan's full allowance applies at once — credits already used this period still count. A downgrade takes effect at the end of the current period.
- Is there annual billing?
- Not at launch. Billing is monthly only.
- What happens if a payment fails?
- There is no grace period. The account moves to the Free plan's limits immediately and stays there until the payment goes through. Your keys keep working on Free, and the plan comes back as soon as you update your card.
- How do I cancel?
- From your account, under manage billing — the Stripe customer portal. Cancelling takes effect at the end of the period you have paid for; the account then moves to Free.
- Is there a trial or a discount code?
- No. The Free plan is the way to evaluate, and there are no promotion codes or coupons.
- What counts as a screen?
- One call to /screen, whatever it returns — two credits for a name that clears and two for a name that hits.
- Can I self-host?
- Under an enterprise contract, self-hosted or bring-your-own-licence. Upstream dataset terms travel with the corpus either way.