In this article
Build reconciliation around the observed execution chain. Technical token production is not automatically paid work for equipment owners.
A simple example has one request and answer. Real systems can add fallbacks, caching, interrupted streaming and different credentials. Token accounting therefore needs the observed chain rather than only the user’s original text.
This control method was checked on November 1, 2026. Adapt it to the gateway and supplier; final charging conditions belong to the specific product and invocation mode, not a universal rule.
Create control events
Use synthetic short output, long input, streaming and an agreed interruption. Assign an application-operation ID and retain available IDs from each layer. Content can remain separate from accounting metadata.
Record time, model, final executor, credential route and status. Represent several attempts separately under one application task. Otherwise expense can be attached to the wrong event or one request counted repeatedly without an understandable execution history.
Read the selected interface’s usage
OpenRouter Support discusses provider data and different model units. Establish which fields the interface returns and when they appear. Streaming and synchronous calls may require different collection procedures.
Text length is not a reliable replacement for usage. Tokenizers, service structure and model behavior affect it. A local count can help diagnose differences if its origin is clearly labelled beside service-reported values rather than silently replacing them.
Compare intermediate and final accounting
LiteLLM Spend Tracking documents internal accounting. Such systems need a known price source and complete request coverage. Their estimate may differ from the external invoice for explainable reasons.
For example, a gateway uses an older price card while the supplier applies current terms. Establish the cause and update the accounting model. Do not conceal the difference by substituting one number without preserving the change history.
Review special cases separately
Test cached portions, reasoning, additional modalities and interrupted answers where relevant. Ordinary-text rules do not apply universally to every API mode; give each special case its own control row.
Define reconciliation period, timezone and late-adjustment procedure. If billing confirmation follows the technical event, retain a visible pending state. Assign each difference a status: cause established, confirmation awaited or correction required. Financial reviewers can then see reconciliation quality without treating uncertain amounts as final charges.
Apply reconciliation to a GPU pool
Equipment-owner settlements need agreed definitions, not only utilization graphs. Technical token output cannot automatically equal paid work.
Prepare with equipment performance measures and complete router cost.