/v1/metrics/summary) returns an at-a-glance overview of your account’s core usage metrics across all of your API keys. It combines your unique agent configurations (from /v1/agents/list) with completion-call counts derived from your request history into one response, so you don’t have to call and aggregate those endpoints yourself.
This is the endpoint to power a usage dashboard: unique agents used, lifetime completion calls, and recent-window activity.
All counts are computed with database count queries, so your totals stay accurate even after your account passes 1,000 lifetime executions (Supabase’s default row cap). Counting rows client-side would silently plateau at 1,000 — this endpoint does not.
Endpoint Information
- URL:
/v1/metrics/summary - Method:
GET - Authentication: Required (
x-api-keyheader) - Rate Limiting: Subject to tier-based rate limits
Response Format
The endpoint returns a JSON object with the following fields:| Field | Type | Description |
|---|---|---|
success | boolean | Indicates the summary was retrieved successfully. |
unique_agents | integer | Number of unique agent configurations you have used. |
total_completion_calls | integer | Lifetime count of completion calls (accurate past 1,000). |
successful_completions | integer | Lifetime count of completions with status "success". |
completions_last_24h | integer | Completion calls in the last 24 hours. |
completions_last_7d | integer | Completion calls in the last 7 days. |
agents | array | Your unique agent configurations, sorted by last used (same as /v1/agents/list). |
timestamp | string | ISO 8601 UTC timestamp when the summary was generated. |
Example Response
Use Cases
- Usage dashboards: Populate headline tiles (executions, success rate, unique agents) from a single, cheap request.
- Accurate lifetime totals: Report true all-time completion counts without transferring — or capping at — thousands of log rows.
- Activity monitoring: Track 24-hour and 7-day completion volume to spot spikes or drop-offs.
- Python
- JavaScript
- cURL
The
agents array mirrors the data returned by /v1/agents/list — the numeric counts, however, reflect true lifetime totals regardless of how many logs exist. For full request logs, use /v1/swarm/logs.