Audit and usage
Read the audit log and the usage ledger for your workspace.
The audit log and the usage ledger are two Platform surfaces that let you see what happened and what it cost. This guide covers reading both.
Read the audit log
The audit log records every read, write, and export, scoped to your workspace. It shows that a record was accessed, never the value.
Entries record an action against a resource reference (an id for a rider, trip, or chat). The reference is a pointer, not the value: rider and trip identities are never shown here. Viewing the audit log is itself an audited admin action.
The log is a table you can filter and page through:
- Filters. Narrow by action, resource type, actor, and date range. Filters apply on the server.
- Columns. Time, actor (email and role), action, the resource type and its reference id, and the outcome (success, denied, or error).
- Paging. Entries are newest first; load older entries to walk back through the history.
Denied attempts show up too, so the log shows who was turned away, not just who got in.
Read the usage ledger
The usage ledger shows turns, tokens, and estimated cost for your workspace, by day.
Costs are estimates, not an invoice. They are computed from published model rates when each turn completes. They show relative spend so you can compare and spot trends; they are not a billing statement.
- Time range. Switch between the last 7, 30, or 90 days, or all time.
- Totals. Turns, input tokens, output tokens, and estimated cost for the range.
- Cost by day. A bar chart of daily estimated cost.
- Routing breakdown. When Auto mode routes a turn to a cheaper or stronger model, the ledger shows how turns were routed and what the routing saved against a single-model baseline.
See also
- Roles and access for who can read these surfaces.
- Access and audit for the public posture behind the audit log.