Credits, Wallet & Billing
Money moves in exactly three steps: you deposit real currency into your wallet, the wallet buys credits (a prepaid spend balance) or a subscription, and requests then draw down that balance. The wallet itself is never charged per request — purchases only. This separation means a leaked API key can drain your credits, but it cannot drain your card.
1Step 1 — Fund the wallet
Console → Payments → Add funds. Two rails, both live:
- Card via Stripe. Minimum
$2. You are redirected to Stripe Checkout; card data never touches MiaRouter — we receive only Stripe's receipt. - Crypto: USDT or USDC on BNB Smart Chain (BEP-20). You get a deposit address and an exact-amount invoice; the scanner credits your wallet after the required confirmations. Send the exact amount — mismatched deposits need manual reconciliation and a support message.
Any BEP-20 transfer is a public blockchain transaction visible to anyone. That is how blockchains work; we do not pretend otherwise.
2Step 2 — Buy credits or a subscription
Credit packs
Payments → Purchase → Credits. A pack costs a fixed USD amount from your wallet and grants a fixed credit balance (the face value shown on the pack — packs are priced with bonus credit built in, and featured packs stack a percentage discount on top). Credits never expire while the feature exists as-is. Current production packs, for orientation:
| Pack | Pays | Credits granted (face value) | Notes |
|---|---|---|---|
| Starter | $2 | $60 | One per user |
| Small | $5 | $140 | — |
| Personal | $10 | $150 + $15 bonus | — |
| Everyday | $15 | $300 + $30 bonus | — |
| Featured | $20 | $500 + $50 bonus | 5% off, featured |
| Team | $80 | $2,500 + $250 bonus | 10% off |
| Enterprise | $3,000 | $500,000 | — |
Subscriptions
Payments → Purchase → Subscriptions. A subscription grants a larger credit allowance for a period (e.g. 30 days), with optional per-window caps (a 5-hour window and a weekly window when configured), and can move you into a billing group (e.g. Premium → svip) with its own group ratio. Subscriptions are bought from wallet balance, activate immediately, and are granted instantly. The refund policy below applies to everything you can buy on this page — read it before clicking.
No payments are refundable — unless you were unable to use even $1 of the service. Being unable to use the service and choosing not to use it are different things, and the distinction is the entire policy. If you have used more than $0 worth of the service, you have incurred costs for us, so we cannot issue a refund. Wallet deposits, credit packs, and subscriptions are all payments, and the same rule covers them all.
3How requests are billed
Every model in the current catalog bills per request: the flat price on the pricing page per API call, regardless of prompt or completion size. A 10-token ping and a 100k-token migration cost the same on the same model. Check a model's card on Model Square — the badge says per request.
Spending order: if an active subscription covers the model, the request draws from the subscription's allowance (window caps apply); otherwise it deducts credits from your balance. Every deduction lands in Usage Logs with the model, tokens, cost, and request ID. If you want a budget, set it on your API keys — the key quota is the enforcement point.
4Free money (the legitimate kind)
- Free Trial. Granted at Telegram verification: 7 days, ~$20 of credits, restricted model list, 5-hour and weekly window caps, one per person (anti-abuse checks include IP reuse). When it lapses, it lapses.
- Referrals. Your profile has an invite link. When a signup you invited verifies on Telegram, you receive the referral credit (currently ~$20 face value). Signup and referral credits are held pending until that verification — abuse economics, not stinginess.
- Check-in. When enabled, a daily check-in on the dashboard adds a small credit bonus. Free, tiny, consistent.
5Reading your balance
Dashboard shows credits remaining; Wallet shows deposited USD. Costs in the console are displayed in USD by display setting (500,000 internal quota units per $1 — you never need to care about that number unless you are reading raw API fields).