Tokens and hosting usage

AI tokens measure input and output work. Hosting usage measures environment running periods. Read these separately before comparing the project's activity with its offer and invoices.

Before you start — Choose the project and the activity you need to understand: AI work or environment running time. Have the request or hosting period available. Read recorded amounts with their period and currency instead of deriving a charge from a token count.

Read the token directions

Read the two token directions separately and retain the category when its recorded use is zero.

1. Open Dashboard and find the token totals.
2. Read the analysis, work and Studio counters separately.
3. Read ↑ as input tokens and ↓ as output tokens.
4. Use the relevant project or request detail for the work concerned.

Both directions remain visible when the count is zero. A zero means no usage is recorded in that counter; it does not remove the category from the display.

Inspect a Studio request's usage

Use the request detail to relate token activity to the work and result concerned.

1. Open the request detail in Studio.
2. Read Tokens alongside its build state and result.
3. Compare input and output separately.
4. Revisit the detail after the work progresses when you need the updated record.

A token count is not a count of completed pages, a delivery estimate or a hosting duration.

Review hosting usage

Identify the environment and billing period before interpreting a duration or amount.

1. Open Infrastructure Billing.
2. Read Summary for each environment.
3. Inspect Current billing periods.
4. Compare Environment, Period, Duration and Amount.

An ongoing period continues to accrue while the environment runs. Production uses the displayed monthly subscription; development and staging use recorded hourly periods.

Understand the billed duration

Compare elapsed time with the hourly-session rounding rule and applicable rate.

1. Find the running period concerned.
2. Read its start and end in Period, the billed hours in Duration and the recorded Amount.
3. Check whether the period is ongoing or closed.
4. Compare the amount with the applicable environment rate.

The billed duration can be explained from the recorded session and its rate.

Note — Each recorded hourly session is rounded up to whole hours, with a minimum of one billed hour. A short running session can therefore show an amount even though its elapsed time is less than an hour.

For hourly sessions, twenty minutes of running time is billed as at least one hour; one hour and ten minutes rounds up to two hours. These examples explain duration only. Apply the environment’s displayed rate and read its recorded amount rather than assuming an example gives the project’s charge.

Confirm an amount due

Use the offer and invoice records to review charges after understanding the corresponding activity.

1. Review the actual application offer.
2. Read hosting billing for infrastructure use.
3. Consult the project invoice list.

Use Invoices for the recorded amount and currency, and Environments when managing test availability.