Payments · 2026-11-12 · 321AI engineering notes · get a key
Quick answer: Card-first billing locks a lot of developers out of AI APIs. Prepaid alternatives solve this: USDT top-ups settle globally in minutes, and regional channels like Alipay cover users who hold no crypto at all. Here is what works on 321AI in 2026, and how settlement treats both failures and leftover balance.
Prepaid changes the risk shape: your exposure is capped at your balance, there is no subscription to forget about, and no card to expire mid-production. On 321AI the wallet is per account, every model draws from it, and the terms state that unconsumed balance is refundable via the ticket system (returned by the original payment route, minus payment-channel fees). Prepaid should never mean trapped.
There is also a procurement angle: prepaid spend is approved in increments you choose, which keeps budgets visible without a purchasing flow for every model experiment. Teams top up a working balance, spend it against itemized logs, and scale the increment when the data justifies it — the approval loop fits inside an engineering team instead of around it.
USDT is supported across four networks — TRON, BSC, Polygon and Solana — so you can fund from whatever chain you already hold on. Funds land in your wallet and apply to all services; there is no per-model allocation to manage. Because billing is prepay-and-settle (below), a modest balance is enough to run real workloads and see the settlement behavior with your own eyes.
Network choice is a cost and speed trade-off: TRON is the common default for smaller amounts, while Polygon and BSC are familiar to EVM-native teams and Solana to those already holding there. The console names the address and network at top-up time — send on the network the console displays, since cross-network transfers are the classic way to lose funds.
The Terms of Service list Alipay among the top-up channels, and the console shows which channels are currently available for your account. The right habit is to check the top-up screen at the moment you fund — availability of regional rails changes, and the console is the source of truth, not a blog post (including this one).
| Step | What happens | What you see |
|---|---|---|
| 1. Pre-deduct | Estimated cost is held when the request starts | Balance drops by the estimate |
| 2. Execute | The call runs on the routed lane | Usage metadata recorded |
| 3. Settle | Actual usage is billed at quoted rates | Difference returns to balance |
| 4. On failure | Request did not complete | Full pre-deduction refunded automatically |
The same semantics apply to every model and every payment channel: only successful calls are billed, and the usage logs itemize tokens, model, cost and status per call so you can audit settlement yourself.
Settlement is also where multi-supplier economics show up in your favor: the lane that served the call bills its own quote, and routing keeps preferring cheap healthy lanes — so the same request can settle at slightly different prices across a day, always at or near the floor you saw. The logs let you reconcile every one of them.
Prepaid concentrates risk in the account, so treat the account like production: one owner, unique password, tokens rotated on schedule, and leaked keys revoked immediately — consumption from a leaked token is borne by the account holder, and that line exists in the terms for a reason. Give each service its own token so a compromise is visible in the logs as one token, not a mystery. None of this is platform-specific discipline, but prepaid makes it cheap insurance.
Billing semantics in full are on the pricing page, the payment lines are in the Terms of Service, and the FAQ answers the short questions. Sign-up includes trial credit: create an account and test with real models first.
TRON, BSC, Polygon and Solana. Funds land in your account wallet and apply to all models and services.
Yes — Alipay is listed in the Terms of Service among top-up channels. The console shows the channels currently available at top-up time.
Unconsumed balance is refundable via the ticket system, returned by the original payment route minus payment-channel fees. Consumed credit is non-refundable.
No. Failed requests are never billed — the pre-deducted estimate is refunded automatically and only successful calls settle.
The console shows the current minimum per channel; start small regardless — a day of real traffic is enough to validate settlement behavior, and unconsumed balance stays refundable.
Live prices: /en/models/ · billing: /en/pricing · setup: /en/guides/ · FAQ