Credits and payments

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. Metering and settlement explains how this reserve and settle loop bills from usage metadata without reading your content.

Model usage is charged at the displayed provider rate with no per-model markup.

The service fee

Buying credits adds a service fee, currently a promotional 5% with a $0.75 minimum, down from the regular 8% with 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.

Promotional pricing can end, so read fee_percent and minimum_fee_usd from GET /v1/billing/catalog rather than hard-coding either number.

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 exist:

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.

Availability and exact limits come from the catalog

GET /v1/billing/catalog returns the live minimum and maximum purchase amounts, the fee percent, the minimum fee, the available packages, and which rails are currently accepting payment. payments_enabled covers card checkout and crypto_payments_enabled covers the crypto invoice; the crypto rail is operator-gated and is not enabled on the production deployment at the moment, so check the flag before offering it. 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 "https://control.anonrouter.ai/v1/balance" \
  -H "Authorization: Bearer $ANONROUTER_MANAGEMENT_KEY"

GET /v1/balance

{
  "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.