Billing and Usage

Token360 meters each model request using the pricing rules published for the selected model. Charges can be reconciled from the response, the console, and billing APIs.

How charges are calculated

The billing meter depends on the model. Common meters include:

input and output tokens;
reasoning or cached tokens where separately priced;
generated images;
audio characters or seconds;
video duration, resolution, or another model-specific unit.

Always use the pricing section of the live model page. A provider's public price is not automatically the price of the Token360 route, and different SKUs of the same model can use different meters.

Estimate versus final charge

Playground estimates are planning aids. Final billing uses measured usage and the active pricing rule after the request completes. Inputs such as output length, generated duration, and provider-reported usage can make the final charge differ from a pre-request estimate.

For asynchronous work, billing may be finalized after the resource first enters a terminal state. Use request-level reconciliation when exact settlement matters.

Request-level reconciliation

Store the request or generation ID returned by inference. Query:

text

1GET /v1/billing/requests/{request_id}

The response indicates whether the request is billed and returns recorded usage and charge components when available. Use this endpoint to reconcile customer-visible jobs, not an estimate reconstructed only from token counts.

Account usage

Use GET /v1/billing for summarized account usage over a time range. Enterprise administrators can filter authorized data by member or API-key display identifier. The console also provides dashboard charts, request details, and CSV exports where available.

Use UTC boundaries when comparing daily API results, API-key reset periods, and daily spend protection.

Wallet and credit

The spendable amount can include:

wallet funds added through top-up or redemption;
approved credit for postpaid accounts.

GET /v1/billing/balance returns the current spendable balance. Enterprise members can use billing capacity managed by the tenant owner; they might not be able to top up or change account-level alerts themselves.

Spending controls

Token360 provides several independent controls:


API-key spend limit	One key	Stops that key when its applicable limit is consumed. Optional reset: daily, weekly, or monthly.
Daily spend protection	Account	Stops new billable calls for the current UTC day when the cap is reached.
Credit limit	Postpaid account	Stops new calls when available approved credit is exhausted.
Low-balance or credit-utilization alert	Account	Sends a warning; an alert does not itself add funds or raise a limit.

The most restrictive active control wins. Raising daily spend protection cannot override an exhausted credit limit.

Investigating a billing discrepancy

Capture the request ID and UTC timestamp.
Compare the response usage with request-level billing data.
Confirm the public model name and pricing rule shown on the model page.
Check whether the request was retried or submitted more than once.
For Batch, inspect aggregated billing and individual output lines.
Contact support with IDs and amounts, never with API-key secrets.