Skip to main content
Use dari activity to read routing activity for your current organization. Commands print JSON so you can inspect them directly or pipe them into jq. Every report requires an RFC 3339 time range:
The overview includes message and model-step counts, provider spend, estimated savings, token and cache usage, model mix, key sources, and API-key activity.

​
Find Filter IDs

List the users, API keys, routers, models, and providers available in a time range:
Extract user IDs with jq:
Pass the returned id to --user-id or --comparison-user-id.

​
Common Filters

Activity commands support these filters:
Statuses are completed, provider_error, selector_error, and aborted. --source-scope accepts a comma-separated protocol list, all, or none. Time-series reports choose a bucket size from the range: 60s, 5m, 15m, 30m, 1d, 7d, or 30d buckets. Override it with --bucket-seconds (one of 60, 300, 900, 1800, 86400, 604800, or 2592000):
A range cannot exceed 366 days, and a report cannot span more than 1000 buckets. Choose a larger --bucket-seconds for long ranges.

​
Authentication

Sign in with dari auth login or set DARI_API_KEY to a Management key. Routing keys cannot read activity. With browser login, pass --organization-id to read an organization other than the current one. Every command maps to a routing activity endpoint on the management API; use either surface.

​
Reports