> ## Documentation Index
> Fetch the complete documentation index at: https://docs.valarhq.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Analytics & savings

> Per-engineer usage, operational metrics, and how ValarCode works out savings against a Claude-only baseline

The **ValarCode** dashboard shows two things: how your coding traffic is doing (who is connected, what is flowing, how it performs) and how much you are saving, with every request priced against what it would have cost on Claude.

The numbers are live. If the usage source is briefly unreachable, the dashboard shows zeros and an "unavailable" badge instead of guessing.

## Key numbers

The setup view shows a 30-day, org-wide strip:

* **Engineers connected**: distinct client ids seen. By default the client id is the engineer's OS username, so the leaderboard reads as real names; teams that prefer opaque ids can connect with `--user-id RANDOM` (see [per-engineer attribution](/valarcode/setup#per-engineer-attribution)).
* **Requests routed**: total coding requests.
* **Tokens**: input, cached, and output.
* **Saved**: dollars saved against a Claude-only baseline (never negative).

## Savings and spend

A 30-day card breaks down the money:

* **Saved this period**, with a "% vs Claude-only" figure.
* **Actual spend**, what you paid across all served models.
* **Claude-only cost**, what the same traffic would have cost at Claude list prices.
* **Spend vs. Claude-only**, a per-day chart of actual against baseline. The gap between the two lines is your savings.

## Operational metrics

With a window selector (1h, 6h, 24h, 7d):

* **Inference volume**: requests by status class (2xx, 4xx, 5xx).
* **Response time**: end-to-end p50, p90, and p99 latency.
* **Rate-limited requests**: requests shed by plan limits.
* **Token usage**: throughput in tokens per second.

## Where your requests went

A served-model mix table shows, for each model, its share of traffic, its request count, and its average savings against the Claude baseline. Rows served by a frontier Claude model show "n/a", since they are the baseline. Models you have configured but that saw no traffic still show up, zero-filled, so nothing is missing from the picture.

## How savings are worked out

Savings compares two numbers for the same traffic, each priced on its own:

* **Actual spend**: the real per-token rate of the model that served each request. Open-weight models use their [catalog price](/pricing), and the frontier Claude tiers use Claude list prices.
* **Claude-only baseline**: what the same traffic would have cost on Claude at list prices. Requests already served by Claude use that tier's own list price.

**Savings = Claude-only baseline - Actual spend**, summed across served models. Both sides use the same basis, which is why Claude-served traffic differences to about \$0: its baseline and its actual cost are the same model at the same price.

<Note>
  Claude-served traffic showing about \$0 in savings is working as intended. Savings show up only when traffic routes to an open-weight model.
</Note>

The baseline uses Anthropic list prices throughout, so both sides of the comparison are priced on the same basis.

## Next steps

<CardGroup cols={2}>
  <Card title="Model routing" icon="route" href="/valarcode/routing">
    Adjust the split and watch savings respond.
  </Card>

  <Card title="ValarCode overview" icon="rocket" href="/valarcode/overview">
    Connect more engineers to grow the sample.
  </Card>
</CardGroup>