Analytics

Understand model usage, settled cost, Resource reliability, custom events, live projections, and durable historical exports.

Analytics answers historical and aggregate questions about Runs, models, Tools, Resource operations, Channels, deployments, Credentials, and custom product events. The Console dashboard uses a bounded recent projection for model calls, tokens, cache use, latency, spend, Agent activity, and Resource reliability.

Analytics is not authoritative live workflow state. A Session exposes current status, waits, controls, journals, and ledger facts. Use a Session’s /workflow endpoint when an operator needs authoritative liveness; use analytics for cross-workflow trends, investigation, cost, and export.

Data guarantees

Audit-critical and billable transitions are durably recorded at the service that owns the underlying fact. Their canonical event IDs are retried into the shared historical archive and deduplicated when queried. Authentication state remains authoritative in Auth, balances and debits in Billing, and Run state in the owning Session; analytics is their centralized projection, not a replacement authority.

Ordinary HTTP request telemetry is best-effort. Recent live views are operational and may contain at-least-once duplicates or omit a point. Historical queries and exports use the durable archive and deduplicate canonical event IDs; use those surfaces for exact cost, margin, billing-evidence, and audit analysis.

Data paths

Choose an interface

Use Instrument custom analytics to add a typed event. Use Query and export analytics for time windows, filters, grouping, raw detail, and artifacts.