How billing works

Quotaflow charges per token against your organization balance, which is the only spendable money account for customer-organization keys. Project budgets are reporting targets, not separate wallets. Per-model unit prices are returned by the authenticated /models response and listed on each model's reference page — treat those as the source of truth for exact rates.

What you are charged for

• Tokens actually processed. Input and output tokens are metered per request at the model's unit price.
• Streaming requests that are cancelled. If your client disconnects before a streaming response finishes, usage that has already been produced is still billed. Quotaflow reads the upstream response through to completion so the amount metered reflects real usage rather than an arbitrary cutoff point.
• Long-context requests, at a surcharge. When a single request's input plus cache-read tokens exceed the model's long-context threshold, that request's input is billed at 2× and its output at 1.5× the normal rate. The threshold varies by model — for example, GPT-5.4 / 5.5 / 5.6 models use 272,000 tokens and several other models (such as some Gemini Pro models) use 200,000. Once the threshold is crossed, the multiplier applies to the whole request.

Caching

A prompt cache hit (cache-read tokens) is billed at a lower rate than normal input tokens, and cache writes are priced separately. Exact cache rates differ by model and are part of each model's pricing — see /models and the model reference pages.

Where to find exact prices

• GET /openai/v1/balance returns your current organization balance and billing context.
• GET /models returns the models your key can use.
• Per-model unit prices (input, output, and cache) are documented on each model's reference page.

<Note>

This page describes billing *behavior*. It intentionally does not hard-code per-model unit prices, which live in /models and the model reference pages so they stay authoritative.

</Note>