---
title: "Get Observability Harnesses"
method: GET
path: "/observability/harnesses"
tags: ["observability"]
---

# Get Observability Harnesses

`GET /observability/harnesses`

Per-harness rollup — the headline table.

Spend, tasks, sessions, session cost percentiles, tokens, models, surface
breakdown, and category-coverage gating.

## 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

- HarnessesResponse — All per-harness rollups plus the data-quality envelope.
  - `harnesses` HarnessRollup[], required
    - `harness` string, required
    - `category_coverage` 'full' | 'partial' | 'excluded', required
    - `spend` number, required
    - `routed_spend` number — Spend for this harness served via the router (USD).
    - `direct_spend` number — Spend for this harness on raw direct-model calls (USD).
    - `task_count` integer, required
    - `session_count` integer, required
    - `one_shot_count` integer, required
    - `median_cost_per_session` number, required — Median ``total_cost`` across ``session`` tasks (one-shots excluded).
    - `p90_cost_per_session` number, required — 90th-percentile ``total_cost`` across ``session`` tasks.
    - `input_tokens` integer, required
    - `output_tokens` integer, required
    - `total_tokens` integer, required
    - `models_used` string[], required
    - `surfaces` HarnessSurfaceBreakdown[], required
      - `surface` string, required — e.g. codex ``desktop``/``tui``/``exec``/``vscode``.
      - `spend` number, required
      - `task_count` integer, 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/versions/31dfe831e079/schema)