The gateway tracks what each request costs and applies budgets per key and per team. This page explains how provider pricing flows through the gateway and where to see the numbers.

​
How provider charges reach the gateway

Each provider bills differently. The gateway records the cost against the key that made the request, using the provider’s price list. For a per-token provider, the gateway uses the published price per million tokens:
A pool can carry more than one price. deepseek-v4.1-flash has four members and only one of them is priced at the figures above — the other three are registered at zero. So the cost of a request to a pooled name depends on which member answered it, and the number in this table is the highest it can be, not the number you will always pay. The per-request truth is in the spend log, not here.
These figures were read from GET /v1/model/info on the running gateway. That route is the authority; this table is a copy and can go stale.
A fixed-price provider shows zero per request. That is correct, not a bug: if the plan is a flat yearly fee, a per-token price has no meaning.

​
Budgets, keys and teams

The gateway controls spend with two mechanisms: Why teams matter for cost: if a route charges per request (like OpenRouter), you may not want every team to reach it. The admin can restrict a route to certain teams. A key from a team without access gets a refusal:
This is a deliberate control, not an error: an admin may allow a trusted team to use a metered route while keeping other teams on flat-rate providers.

​
Where to see the costs

The admin dashboard at https://llm.hjc925.cloud/ui shows the numbers: The request log keeps refused requests too. A refused request shows zero tokens and zero cost, so you can see when someone tried a model their team cannot use.

​
What to watch for

Look at which model jumped. A heavy job pointed at an expensive model, or a looping agent, both show up as a spike against one key.
The gateway stops the key and returns a budget error. Decide whether to raise the limit or leave it stopped.
Restrict the route to the teams that are allowed. Access control is the lever; the log shows who tried and was refused.