> For the complete documentation index, see [llms.txt](https://vibemx.gitbook.io/neuronai-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vibemx.gitbook.io/neuronai-studio/analytics/usage.md).

# Usage Analytics

NeuronAI Studio surfaces lightweight usage signals on existing screens. It does not add a separate analytics dashboard.

## Dashboard

The Dashboard shows total tokens and estimated cost for the last 30 days. Nested agent runs are excluded from the window query because their usage is already rolled into the parent workflow run. Recent runs also show tokens and estimated cost.

## Debugger

Trace lists show compact total-token values. Trace details show prompt, completion, and total tokens plus estimated cost. LLM spans include provider, model, tokens, and cost in the timeline and step detail.

## Test Pretty view

Completed workflow and agent messages show run-level tokens and estimated cost. Agent and LLM workflow steps show their own usage next to duration. Older trace payloads without usage fields continue to render without chips.

The currency comes from `neuronai-studio.usage.currency`. Costs are estimates based on the configured model rates, not provider invoices.

## Host metering

Use the [Usage Export API](https://github.com/digitalelvis/neuronai-studio/tree/main/docs/guides/analytics/export-api.md) for host-facing aggregates and per-run reconciliation. Studio surfaces above are for operators only.

## Related

* [Cost Estimation](/neuronai-studio/analytics/costs.md)
* [Dashboard](/neuronai-studio/guides/dashboard.md)
* [Runtime & Traces](/neuronai-studio/workflows/runtime-and-traces.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://vibemx.gitbook.io/neuronai-studio/analytics/usage.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.