---
title: "Get Observability Keys"
method: GET
path: "/observability/keys"
tags: ["observability"]
---

# Get Observability Keys

`GET /observability/keys`

Per-API-key rollup, ordered alphabetically by key name (never by spend).

## Query parameters

- `start_date` string, nullable — Range start (ISO date or datetime, UTC). Defaults to 30 days ago.
- `end_date` string, nullable — Range end (ISO date or datetime, UTC). Defaults to now.
- `scope` 'team' | 'personal' — ``team`` (default) aggregates the active team's coding-agent tasks; ``personal`` narrows to tasks on keys the requesting user created.

## Response `200`

Successful Response

- KeysResponse — All per-key rollups (alphabetical by name) plus metadata.
  - `keys` KeyRollup[], required
    - `api_key_id` string, nullable, required
    - `api_key_name` string, nullable, required
    - `key_creator_user_id` string, nullable, required
    - `key_creator_name` string, nullable — Display name of the team member who created the key.
    - `key_creator_email` string, nullable — Email of the team member who created the key.
    - `spend` number, required
    - `routed_spend` number — Spend for this key served via the router (USD).
    - `direct_spend` number — Spend for this key on raw direct-model calls (USD).
    - `total_tokens` integer, required
    - `task_count` integer, required
    - `primary_harness` string, nullable, required — Harness family with the most spend for this key.
    - `primary_router_type` string, nullable — Router this key mostly relies on ('direct' when it bypasses the router).
    - `category_mix` KeyCategorySlice[], required
      - `category` string, required
      - `spend` number, required
  - `meta` ObservabilityMeta, required — Data-quality envelope attached to every observability response. Lets the UI label boundaries instead of silently under-reporting: the category window (classification only runs over recent inline payloads), the per-harness payload coverage, and the earliest date harness attribution is available (before which no data exists, so a picker must not offer it).
    - `category_window_days` integer, required — Category classification only covers the last N days of inline payloads.
    - `category_window_start` string, date-time, required — UTC start of the category-classification window (now - category_window_days).
    - `coverage_start_date` string, date-time, required — Earliest UTC date with caller metadata / harness attribution; date ranges before this return nothing.
    - `harness_coverage` HarnessCoverage[], required — Per-harness category-coverage gating for UI labelling.
      - `harness` string, required
      - `coverage` 'full' | 'partial' | 'excluded', required
    - `generated_at` string, date-time, required — UTC time this response was computed.

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/pioneer/apis/brain-api.md) · [All operations](https://skmtc.net/pioneer/apis/brain-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pioneer/brain-api/revisions/31dfe831e079/schema)