Pricing
The unit is the enrichment, not the request
A batch of a thousand descriptors is one HTTP call and a thousand units of work. Billing per request would let a caller pay for one and consume a thousand, so usage counts enrichments and the usage endpoint reports both numbers.
| Tier | Included | Overage | Who it is for |
|---|---|---|---|
| Free | 5,000 / month | Hard stop | Evaluate without talking to anyone. Enough for one statement of the largest size we read. |
| Starter | 100,000 / month | Metered | An indie fintech's live volume. |
| Growth | 1,000,000 / month | Metered, lower rate | A funded startup's live volume. |
| Enterprise | Custom | Custom | Volume commitments, data residency, SLA. |
The per-enrichment prices are not published yet. The structure above is settled and the free tier is real: it needs no card and no conversation, and 5,000 enrichments a month is enough to run a full statement through and see what you get back. The allowance belongs to the account, so all of its keys and the console share it. If you know your volume and want a number, sign up and tell us what it looks like.
Start now
No card, no call, no sales cycle
Sign up with an address and a password, and make a key in the console in one click, so you can price this against your own volume rather than against an example.
Nothing is charged today and there is no card on file to charge. What the meter counts is the enrichment, not the request, so a batch of a hundred is a hundred.