How billing works
apiToken.sale billing is prepaid: you top up a balance once and every GPT and Gemini request draws it down. Each call is metered at the provider's official rate card, your flat 50% B2C discount is subtracted, and only the net amount touches your balance.
·
One prepaid balance for GPT and Gemini
Billing on apiToken.sale is prepaid and pay-as-you-go: you fund a balance in advance, and API requests draw it down — there is no monthly invoice and no customer subscription. The same balance covers every supported GPT and Gemini model, GPT Image included, so you never manage separate OpenAI and Google accounts or two separate bills.
You top up any whole-dollar amount. The balance never expires, which changes how you should fund it: there is no reason to preload a large sum "just in case", and no reason to hoard either. Add what the next few weeks of work need, and top up again when the dashboard says you are running low. Idle time costs nothing — a balance you do not spend this month is still there next quarter.
See also: GPT API pricing: input, cache, output and long context
How a single request becomes a charge
Every call is priced from the usage the provider actually reports, not from a flat per-request fee. The router converts the response's usage fields into official provider spend, leg by leg:
- Input tokens — your prompt, system instructions and conversation history, at the model's official input rate.
- Output tokens — the model's reply, at its official output rate, which is usually higher than input.
- Cache legs — cache writes and cache reads are metered separately from regular input, and cache reads are much cheaper.
- Model-specific buckets — long-context surcharges or image legs where a model's rate card defines them.
Because metering follows each provider's own rate card, a GPT request is priced exactly like OpenAI would price it and a Gemini request exactly like Google would — before your discount enters the picture. Streaming responses are metered the same way as non-streaming ones; the final usage arrives with the stream, and the charge is identical.
Where the 50% discount enters the math
The discount is applied after official spend is computed, never before. Official spend comes first, then your flat 50% B2C discount is subtracted across every supported provider, and the net amount is deducted from your prepaid balance. A worked example on GPT-6.1 Terra (official $1 per million input tokens, $5 per million output tokens):
| Step | Calculation | Amount |
|---|---|---|
| Input leg (3,000 tokens) | 3,000 × $1 / 1M | $0.003 |
| Output leg (800 tokens) | 800 × $5 / 1M | $0.004 |
| Official provider spend | $0.003 + $0.004 | $0.007 |
| Flat 50% B2C discount | $0.007 × 50% | −$0.0035 |
| Deducted from your balance | $0.007 − $0.0035 | $0.0035 |
The same order of operations applies to every GPT and Gemini model against its own official rate card. Prompt caching compounds with the discount rather than replacing it: a cache read is already cheaper at the official rate, and the 50% comes off that cheaper figure too.
Funding the balance: cards, crypto and amounts
At checkout you can pay by bank card or with cryptocurrency through a secure payment provider; crypto top-ups credit once the network confirms the transaction. Either way the funds land as prepaid balance in your account and are spent only when requests run — you can switch between card and crypto per top-up.
Refund handling is processed through the original payment provider.
What happens when the balance hits zero
Requests start failing with HTTP 402 — insufficient_quota on the OpenAI-compatible lane, FAILED_PRECONDITION on the native Gemini routes. Your key is not revoked and your account is not closed; the calls simply stop going through until you top up. Any whole-dollar amount restores service immediately, so the fix is a checkout visit, not a support ticket. Do not retry 402 as if it were a 429.
curl https://router.apitoken.sale/v1/chat/completions \
-H "Authorization: Bearer sk-pool-•••" \
-H "content-type: application/json" \
-d '{
"model": "gpt-6.1-terra",
"messages": [{"role":"user","content":"ping"}]
}'
# With an empty balance the response is:
# HTTP 402 insufficient_quota — the account balance is insufficientFor unattended workloads — agents, cron jobs, CI evals — check the dashboard balance before long runs. A 402 mid-queue is a failed job, and retries cannot fix an empty balance the way they fix a rate limit.
Auditing where the money went
Dashboard Usage shows settled spend by model, provider, day, and customer key. The ledger remains the money journal of charges and top-ups. For a request-level audit, call GET /activity with a customer key; it returns model, provider, tokens, charged amount, public error, and optional agent session grouping.
To plan a top-up rather than reconcile one, estimate the workload first: per-model official and discounted rates are listed on the model pages, and the cost calculator turns a prompt-plus-reply token estimate into a dollar figure before you spend anything.
Frequently asked questions
Is apiToken.sale billing prepaid or postpaid?
Prepaid. You fund a balance in advance in any whole-dollar amount, and requests draw it down — there is no monthly invoice and no subscription.
Does one balance cover GPT and Gemini?
Yes. Each provider is metered against its own official rate card, the same flat 50% B2C discount applies, and the net charge draws from one shared prepaid balance.
How is the 50% discount calculated per request?
The request's usage legs (input, output, cache and any model-specific buckets) are converted to official provider spend first; then 50% is subtracted, and only the remainder is deducted from your balance.
What happens when my apiToken.sale balance runs out?
Requests return HTTP 402 with an insufficient-balance error. Your key stays valid — topping up any whole-dollar amount restores service immediately.
Does unused balance expire, and can I get a refund?
Balance never expires; unused funds simply remain available. Refunds are handled through the original payment provider — contact support via Telegram or at apitokensale@gmail.com.
Can I see token-level usage for each request?
Yes. Call GET /activity with a customer key. It returns each request with its model, provider, tokens, charged amount, public error, and optional agent session grouping.
Create an account, top up your balance, and generate an API key to use supported GPT and Gemini models.