Website activity metrics

The website displays aggregate token and agent-session counts from a background collector. This is a website endpoint, separate from the Mystro agent API.

Read the snapshot

GET /api/public/metrics on the website origin returns a JSON snapshot without authentication. Only aggregate counts and an update timestamp are exposed; no prompts, customer identifiers, credentials, or session records are returned.

{
  "tokensProcessed": 1420250141,
  "agentSessions": 1239,
  "updatedAt": "2026-09-09T08:00:00Z"
}

Counts are nonnegative integers. updatedAt is the last successful collection time, not the time the browser fetched the endpoint. Before a usable snapshot exists, the endpoint returns 503; the page retains its last good figures.

Collection and caching

A background collector reads usage from retained backend transcripts, deduplicating messages and sessions in a durable local ledger. Requests serve the snapshot; they do not scan transcripts. Token usage includes input, output, cache-creation input, and cache-read input tokens, taking the maximum observed total per message ID. Transcript trimming means records already missing before collection begins cannot be recovered.

The browser stores a validated snapshot in localStorage for five minutes. It displays cached figures while checking for updates when stale, refreshes while visible, and keeps the last successful values on network failure. Storage denial falls back to memory. Older or invalid responses cannot overwrite newer cached data. The response is also cached server-side for 60 seconds.

Counters preserve the particle opening and animate toward refreshed totals. Reduced motion applies updates immediately.

Website endpoint contract