Skip to main content
Measuring every token, every request, every compression event, every routing decision, at session level locally and at team level in the managed Edgee console.

​
Read usage in the console

Start in Activity for organization trends, Team for member or squad costs, Sessions for one agent run, and Logs for one model request. Select the same organization, period, and filters before comparing values.

​
Activity

Review costs, requests, token volume, and savings over the selected period. Displayed usage cost is not necessarily a deduction from Edgee credits, including when using a provider subscription or BYOK.
Activity showing organization usage over time.

Local demonstration with fictional members and illustrative usage data.

​
Logs

Filter to the affected period, key, model, or provider. Open a request to compare the model requested with the model served, token counts, latency, cost, and errors. A reroute explains a model difference; a fallback can explain a provider change after an error.
Request logs with model, provider, tokens, latency, and cost.

Local demonstration with fictional members and illustrative usage data.

Full payloads are available only when Debug captured them. Enabling Debug later does not reconstruct earlier requests.

​
Investigate an unexpected bill

  1. Find the period with the increase in Activity.
  2. Identify the member or squad in Team.
  3. Open their sessions and inspect the most expensive requests.
  4. Check routing, cache usage, model/provider, and the billing mode.
  5. Adjust the appropriate strategy or limit, then verify new requests.
To send usage records to your infrastructure, configure an observability destination.

​
Application usage

For SDK response metrics and request tagging in application code, see Application observability. Request tags, token usage, and compression metrics are covered in the LLM Router & SDKs section.