Credit-based developer billing
Fund the wallet. Spend it on live API work.
Developer and API billing is wallet-funded. Teams add credit in hosted checkout, completed production runtime decisions burn that balance at the public rate card, and sandbox traffic stays free. Minimum purchase starts at $10.00.
Developer wallet
Fund credits, then let runtime burn them.
Developer and API billing runs through wallet credit. Hosted checkout starts at $10.00, sandbox traffic stays free, and only completed production decisions consume balance.
Available balance
Sign in to view
Production credit floor
$10.00
Projected after period
Wallet-based
Funding lane
Sign-in required
Minimum purchase $10.00. This funds the developer wallet, not the main web billing surface.
Sign in to buy creditsFunding model
Developer pricing runs through one credit wallet.
This is not the main web-app billing surface. Developer and API usage uses funded wallet credit, live request metering, and contract overrides only when finance asks for them.
Entry
$10.00 minimum wallet purchase
Signed-in developers can top up the API wallet in hosted checkout without touching the main web-app pricing surface.
Production floor
Keep $10.00 available for live issuance
Production keys and live runtime traffic depend on funded balance, delinquency recovery, and your configured credit controls.
Free environments
Sandbox, staging, and JWT console traffic stay off the meter
Only completed production API-key decisions in the public request families consume credit.
Contract lane
Enterprise keeps the same APIs with negotiated rate overrides
No separate integration path is required when a team moves from self-serve wallet funding to contract billing.
01
Frontend protection
Rate limiting, WAF evaluation, and signup protection on completed production API-key decisions.
$0.90
/ 10,000 requests
02
Backend verification
IP intelligence and email validation on completed production API-key decisions.
$3.50
/ 10,000 requests
free lane
Sandbox and test traffic
JWT console tests, sandbox keys, and non-production environments stay analytics-only.
Example period
Production and sandbox traffic by day
Usage calculator
Estimate spend from request volume.
Sandbox exploration
Team validating auth, payload shape, and policy behavior before live cutover.
Sandbox traffic stays free and does not burn wallet credit.
$0.00
free
Production storefront
WAF, rate limiting, and signup protection for a fast-moving web property.
250.0k frontend requests during the current billing period.
$22.50
estimated usage cost
Verification-heavy backend
Email validation and IP intelligence across auth and fraud flows.
90.0k backend verification requests during the current billing period.
$31.50
estimated usage cost
Billing flow
How runtime spend moves through the wallet.
01
Runtime decision lands
A production protection or verification request hits the API.
02
Usage family is stamped
Cosantoir records the request family, environment, and billable units.
03
Wallet burn is projected
The developer wallet updates projected balance, thresholds, and production readiness before the period closes.
04
Ledger and invoices settle
Purchases, enterprise overrides, and end-of-period invoices reconcile against the same request-metering engine.
Policy notes
What gets billed and what stays free.
Developer wallet purchases start at $10.00.
Only completed production API-key requests consume wallet credit.
Sandbox keys, staging traffic, JWT console tests, and auth failures remain analytics-only.
Enterprise can switch to contracted rates or invoicing without changing request paths.
FAQ
Questions teams ask before launch.
Why is there a $10 minimum purchase?
The wallet needs a funded starting balance before live issuance and production runtime checks can operate safely. Smaller one-off purchases do not keep the production floor stable enough for real traffic.
What actually spends credits?
Completed production requests in frontend protection and backend verification spend credit at the published rate card. Sandbox, staging, and JWT console usage stay free.
When do I see wallet changes?
Top-ups appear through the hosted checkout ledger, and projected available credit updates in the billing console during the active billing period before invoices settle.
Can enterprise skip self-serve top-ups?
Yes. Contracted teams can keep the same APIs and metering engine while finance moves onto negotiated rates, invoicing, or committed credit structures.