Billing
Users pay through a credit balance. Every API request deducts from the balance based on input and output token counts.
Platform margin
Section titled “Platform margin”A 6% platform margin is added on top of the requested top-up amount.
Requested: $10.00Margin (6%): $0.60Charged: $10.60Examples for small first payments:
| Credit added | Platform margin | Amount charged |
|---|---|---|
| $5.00 | $0.30 | $5.30 |
| $10.00 | $0.60 | $10.60 |
Token pricing
Section titled “Token pricing”Prices are quoted per 1M tokens in USD. Some models use input cached, reasoning tokens, image, or audio second units.
Example price units:
| Unit | Example value | Note |
|---|---|---|
per 1M tokens | $5.00 | Text input/output |
per image | $0.002 | Image generation |
per second | $0.0008 | Audio/video |
per minute | $0.048 | Realtime audio |
per 1M token-hours | $3.20 | Cache |
Check the current price per model at Dashboard > Models.
Reasoning tokens
Section titled “Reasoning tokens”On reasoning/thinking models (e.g. Z.AI GLM, the Google Gemini thinking series) the reasoning tokens the model generates are billed as output tokens — even though they do not appear in the response text. A short answer can therefore consume more tokens than expected because of the reasoning produced behind it.
For transparency, the response usage block breaks this out:
{ "usage": { "prompt_tokens": 20, "completion_tokens": 596, "total_tokens": 616, "completion_tokens_details": { "reasoning_tokens": 575 } }}completion_tokens already includes reasoning tokens; reasoning_tokens only shows how many went to
reasoning. prompt_tokens + completion_tokens = total_tokens always holds.
To keep costs down, keep thinking opt-in: GLM models default to off
(Z.AI Thinking Control) and only reason with the :think suffix or reasoning: true.
Balance and history
Section titled “Balance and history”Dashboard > Billing shows:
- Live balance
- Top-up history (amount, margin, date)
- Per-request deductions
- Monthly spend summary
Top-up methods
Section titled “Top-up methods”The target dashboard method is:
- Credit card or another supported payment method through a secure checkout page.
Manual bank transfer is handled only after support approval as an operational exception. Crypto top-up is not part of the public checkout flow.
Insufficient balance
Section titled “Insufficient balance”If the balance cannot cover a request, the API returns 402 insufficient_balance. No tokens are consumed.
{ "error": { "message": "Insufficient balance. Top up required.", "type": "insufficient_balance" }}