Usage statistics
Tokens and requests by user, team, model and day, with CSV export.
Every request through Memtro is recorded with who made it, which model answered after routing, and the input and output tokens the provider reported. Dashboard → Usage turns that log into statistics for the last 7, 30 or 90 days, or the current month.
What you see
- Totals for the period: requests, input tokens, output tokens, tool calls.
- By day: a bar per day, input and output stacked, so spikes are easy to spot.
- By user: every member's requests and tokens, with their teams, sorted by volume. Scheduled jobs count towards the person who owns them.
- By team: the same figures rolled up per team. A member of several teams counts towards each; people in no team appear as "No team".
- By model: the model that actually answered, after
autorouting, so you can see where the tokens go.
Export any period as CSV from the page, or fetch it directly:
curl -b <session> "https://platform.memtro.com/api/usage/export?range=30d"
Who can see what
Admins, and users whose team grants View organisation usage, see the whole organisation. Everyone else sees their own usage only. See Teams and permissions.
What counts
Requests from the Chat page, the API, scheduled jobs, the MCP server's engines (OpenCode, Claude Code) and client tools are all logged under the user whose key or session made them. Token counts come from the provider's own usage report for the request; embeddings used for memory are not counted. Memtro does not price tokens, since usage is billed by your providers under your keys, but the per-model table makes the provider invoices easy to attribute.