Billing and credits
Authpermit bills two ways: a plan for the platform, and credits for the operations that cost something to perform. Recurring resources — endpoints, servers, monitored vendors — are metered by the platform counting what it already holds, so the invoice matches the inventory in your console rather than a number you declared.
Credits
100 credits to the dollar, with volume breaks at 10,000 (15%), 100,000 (30%) and above. Each billable operation has a published price:
| Operation | Credits |
|---|---|
| Credential issuance | 1 |
| Credential verification | 2 |
| Security scan | 5 |
| Biometric comparison | 8 |
| Basic document verification | 10 |
| Identity verification (document, face, liveness, risk) | 25 |
| Organization verification (KYB) | 30 |
| High-assurance verification | 40 |
| Background check | 80 |
The ledger
Credits are an append-only ledger, not a counter. Every entry records the operation that caused it and the balance after it, so a disputed charge traces back to the request that made it, and a correction is a new entry rather than an edit. Running out returns insufficient_credits rather than proceeding on the house — you are never billed for something you did not agree to.
What is free
Two things cost nothing, deliberately.
- The sandbox. An environment you cannot build against without paying is not a sandbox.
- Deterministic test subjects. Operations against
TEST_IDENTITY_VERIFIEDand its siblings are free wherever they run, including production, because they exist so you can prove your integration end to end.
Both still write a usage event, so the activity is visible in your logs.