> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasiko.com/llms.txt
> Use this file to discover all available pages before exploring further.
# TokenOps
> How Nasiko tracks token spend per agent and per model.
Every LLM call the platform makes — an agent answering a query, the routing engine's selection call, a MAF workflow's per-step calls — reports its token counts through the same telemetry as [observability](/product/observability). TokenOps turns those counts into cost.
## How a token count becomes a dollar amount
Token counts are applied to a per-model price lookup: an input and output rate per million tokens, versioned by effective-date window so a price change doesn't re-cost historical spend. A model with no matching entry falls back to a built-in table rather than reporting zero.
The routing engine's selection call is metered like any other, not folded into the chosen agent — so routing cost is its own line item.
## Where you see it
The **TokenOps** screen is the everyday view: a KPI strip, a searchable per-agent cost table with CSV export, and a token-usage breakdown. See [the TokenOps dashboard](/product/tokenops).
Two API routes back the same and deeper data. They're named `finops` in the API — TokenOps is the product name for what they power.
| Method | Endpoint | Purpose |
| ------ | ------------------------------------- | ---------------------------------------------- |
| `GET` | `/api/observability/finops/dashboard` | Aggregate cost dashboard data |
| `POST` | `/api/observability/finops/insights` | LLM-generated narrative summary over that data |
`finops/insights` returns a short narrative rather than numbers — useful for a weekly digest or an at-a-glance "what changed."
## Related
The traces this cost data rides on.
The day-to-day view.