Credits and payments
Prepaid credits, the service fee, card and crypto top-ups, and reading your balance.
AnonRouter runs on prepaid credits. One credit is one US dollar. Your balance is denominated in USD, and inference draws down against it.
How usage is charged
Text models are billed per token. Image generation is a flat price per image, and speech is priced per character. Each request first reserves a worst-case amount from your balance, then settles to the actual usage the provider reports. Because settlement can only lower the reserved amount, inference can never take your balance negative.
Model usage is charged at the displayed provider rate with no per-model markup.
The service fee
Buying credits adds a 12% service fee, subject to a $1 minimum. The fee is shown as a separate line item before you pay. It applies to credit purchases only, not to individual inference requests.
Buying credits
Credits are purchased from the dashboard, not through the API. Preset packages are $5, $10, $25, $50, $100, and $250, and you can enter a custom whole-dollar amount up to $1,000.
Two payment methods are supported:
- Card. A hosted checkout through a third-party card processor.
- Crypto. An invoice through a self-hosted crypto payment processor, payable with Bitcoin on-chain or Bitcoin Lightning. A crypto quote is valid for 15 minutes. Your order moves to paid once the payment is confirmed on-chain.
Exact limits come from the catalog
GET /v1/billing/catalog returns the live minimum and maximum purchase
amounts, the fee percent, the minimum fee, and the available packages. Read
those values rather than hard-coding them.
Crypto is not automatically anonymous
Paying in crypto does not by itself make a purchase anonymous. Public blockchains and payment infrastructure can observe the limited data described in the privacy policy.
Reading your balance and usage
A management key can read your balance and usage programmatically.
curl "$ANONROUTER_BASE_URL/balance" \
-H "Authorization: Bearer $ANONROUTER_MANAGEMENT_KEY"{
"account_id": "acct_...",
"available_usd": 42.5,
"reserved_usd": 0.0,
"updated_at": "2026-07-30T12:00:00.000Z"
}GET /v1/usage returns a list of recent requests as metadata only, each with
request_id, model, operation, token counts, cost_usd, status, and
latency. Add ?workspace_id=<id> to scope it to one workspace.
Receipts and orders
With a session, the dashboard exposes order and receipt history:
| Method | Endpoint | Description |
|---|---|---|
GET | /v1/billing/catalog | Packages, limits, fee, and payment terms |
GET | /v1/billing/orders | List purchase orders |
GET | /v1/billing/orders/:orderId | Poll a single order's status |
GET | /v1/billing/receipts | List receipts |
GET | /v1/billing/receipts/:receiptNumber | Fetch one receipt |
To watch a purchase complete, poll the order until its status becomes paid
and credited_at is set.