Pricing

Most AI platforms make you commit before you build: a monthly subscription, a credit card on file, an email to verify. Solrouter does none of that. You pay per API call from a balance you fund yourself, so you only ever spend what you use.

The setup is short. Connect a Solana wallet at solrouter.com/sdk, fund your balance with USDC or $ROUTER, generate an API key, and start building. Every product (the Privacy SDK, Agent Privacy API, MCP server, and chat app) draws from that same prepaid balance.

Feature status

Payment methods

You can fund your balance two ways. The difference is what each one means for you and for the token.

Per-call rates

Two rate tables exist in code. Table A bills the chat app and POST /agent. Table B bills the REST route POST /api/v1/chat/completions. GET /payments/pricing is the live source for table A.

Table A: chat and /agent billing. Rates are USD per 1M tokens, before a 20% margin. The balance is held as app tokens at 1,000 app tokens per USD. Each billed direction has a floor of 10 app tokens ($0.01), so a normal inference costs at least $0.02. Charges settle in $ROUTER first and fall back to USDC.

Table B: POST /api/v1/chat/completions. Rates are USD per 1M tokens. No margin and no floor apply. Token counts are estimated from character counts (about 4 characters per token). The cost is debited from your USDC balance only. The route answers 402 when your USDC balance is zero, even if you hold $ROUTER.

The two tables disagree on gpt-oss:20b. Unifying them is a backend follow-up. x402 route prices come from the manifest at https://api.solrouter.com/.well-known/x402.

x402 keyless payments

An autonomous agent often has no human around to sign up for an account or manage an API key. x402 solves that: it lets an agent pay for each call on its own, with no registration at all.

x402 is a standard for HTTP-native micropayments (payments built into the web request itself), settled in USDC on Solana mainnet. The live manifest advertises Coinbase (api.cdp.coinbase.com/x402) as the facilitator. The manifest shows X402_FACILITATOR_URL when it is set, or a built-in default when it is not. It does not show which facilitator settles payments. Any x402-aware agent can discover the payment manifest and start paying immediately.

• Discovery: https://api.solrouter.com/.well-known/x402, the x402 paywall manifest listing available endpoints and pricing.
• Endpoint: POST /api/v1/x402/chat/completions. Arcium-encrypted prompt in, encrypted response out.
• Price: $0.005 per call. Solrouter's server verifies and settles the USDC payment through its facilitator and then returns the reply.
• Best for: autonomous agents that self-fund their own inference costs without a human managing API keys.

Going keyless costs you no privacy. The x402 path runs the same end-to-end encrypted inference as the API-key path: your prompt is still encrypted with Arcium's RescueCipher before it reaches Solrouter's backend.

Managing your balance

You can read your current balance straight from the SDK, so an agent or app can check funds before it spends and top up when it runs low.

const { balance, balanceFormatted } = await client.getBalance();
console.log(`Balance: ${balanceFormatted}`);

To add funds, visit solrouter.com/sdk and connect your Solana wallet. Deposit USDC or $ROUTER. Deposit minimum: not determined.

$ROUTER buyback and burn

Status: Soon. The mechanism exists in code. The ratios are runtime settings, and the worker skips its run while they are zero.

• A buyback worker reads the USDC inflow for each window and buys $ROUTER with a configured share of it (BURN_USDC_BPS).
• A configured share of the $ROUTER bought back is burned (BURN_OUTPUT_TOKEN_BPS). The rest stays in treasury.
• A configured share of fees paid directly in $ROUTER is burned on receipt (BURN_TOKEN_BPS). The rest stays in treasury.

Configured ratios: not published. GET /payments/buyback/log returns the recent buyback worker ticks, including skipped ones. See /docs/token for the token supply schedule and vesting details.