Billing and usage

Tutujin API charges for actual usage: your balance is in CNY, with no monthly fee or minimum spend. Most models are billed per token, with input and output priced separately; some, such as image generation models, are billed per request. Every request's model, group, tokens and cost are recorded in Logs in the console.

Two billing methods

Which method a model uses and what it costs is shown in the live price list under Models and pricing. The same model costs different amounts in different groups — see Choosing a group.

Token billing in detail

The cost of one request:

cost = uncached input tokens ÷ 1,000,000 × input price
     + cached input tokens ÷ 1,000,000 × cache-read price
     + output tokens ÷ 1,000,000 × output price

For example, a support bot sends 2,000 tokens of prompt and history and gets a 400-token answer, 50,000 times a month:

If the system prompt never changes and the model supports context caching, most of the input can be billed at the cache price. Same volume, assuming 1,500 of the 2,000 input tokens hit the cache:

Each vendor decides when the cache hits; the usage field shows how much actually did. The mechanics are in What context caching is and how it saves money.

Per-request billing

Per-request models charge a fixed amount per call, regardless of prompt length. For example, 1,000 images from a per-request image model:

Not every image or audio model is billed per request; some charge for input and output tokens instead. The price list is the reference, and Logs let you check every charge line by line.

Where to see usage

• The usage field in each response: Chat Completions returns prompt_tokens and completion_tokens, plus prompt_tokens_details.cached_tokens on a cache hit; Claude Messages returns input_tokens, output_tokens and cache fields.
• Logs in the console: every request with time, key, model, group, tokens and cost, with filters and CSV export for reconciliation.

Whether a failed request was charged is shown by the records in Logs. For splitting costs by project and closing each month, see Cost allocation and reconciliation.

Balance and spending limits

• The balance belongs to the account and all keys share it. When it runs out, requests return 403 with the code insufficient_user_quota.
• Each key can have a spending limit; once reached, that key returns 401 and other keys keep working. Use it to cap each project or contractor.
• Charges use the price in effect when the request is made.

Invoices

We issue both China domestic invoices (fapiao) and overseas invoices: add our WeChat support JsnonoChat and send your order number.