Skip to main content
Token counts become dollars by looking up a per-model rate that was in effect when the call happened. A later price change never re-costs last month.

Rate lookup

For each model Nasiko knows:
  1. A versioned price book row: input and output rate per million tokens, with an effective-date window.
  2. If no row matches, a built-in fallback table is used and the cost is marked estimated.
  3. Nasiko never reports a null cost. Unknown rates still produce a number, flagged as estimated.
The TokenOps KPI tooltip shows how much of the window is estimated and how many operations had unknown pricing confidence. An estimated figure is a real cost priced at a fallback rate, not a guess at usage. Cache-read and cache-write tokens use the provider’s cache rates when the book has them.

Where the book is filled

On a self-hosted open-source server, the book is seeded with the models Nasiko ships. Optionally, at boot Nasiko can sync published rates from the Portkey price book into its own price book. That sync is fail-open: if it cannot reach the network, existing rows stay. Custom providers you register (LiteLLM, vLLM, Ollama, Azure, Bedrock, OpenRouter, an internal gateway) need a rate before TokenOps can price them precisely. Until a row exists they fall through to the built-in table and show as estimated. Superusers add mappings with the model registry and provider catalog; see Providers.

CLI

providers is the same catalog the LLM router screen uses. Models listed without a rate still route; their TokenOps line is estimated until a rate exists.