Observability
Usage analytics
Every request logged with tokens, cost, latency and attribution.
Each request is logged with everything you need to understand spend and behavior. The usage log records, per request:
user_id,organization_id,workspace_idmodel_id,providerinput_tokens,output_tokens,cached_tokens,cache_hitcost_usd, plusplatform_costandmargin_multiplierfor platform keysresponse_status,response_time_ms,stream_modeauto_mode_tier— the tier auto-mode selectedkey_source—tenantorplatformclient_source— e.g. Cursor, Zed, Qwen or your appcorrelation_id(ULID) andtimestamp
In the dashboard, analytics break down tokens, spend and model mix per user, team and provider, under Analytics.
Logging is written asynchronously through a durable queue keyed by the correlation id, so the request hot-path stays fast.