---
title: "Curated read-only operational state for an external ops agent"
method: GET
path: "/api/v1/operations/summary"
tags: ["Operations"]
---

# Curated read-only operational state for an external ops agent

`GET /api/v1/operations/summary`

## Request

- Base URL: `https://api.daystruct.ai`
- URL: `https://api.daystruct.ai/api/v1/operations/summary`
- Auth: HTTP bearer

One compact, machine-facing projection of production state: system health and dataset counts, per-databank counts and freshness, evidence depth and corroboration, refinery candidate and acquisition queues with the node's own blockers, recent agent activity, request and routing activity, recent failures, agent usage and cost against the daily budget, and an explicit status plus timestamp for every section. Reading it is side-effect-free: it does not refresh research state, advance approval deadlines, queue or run work, change canonical data, or deploy anything. It omits secrets, credentials, private configuration, operator conversations, approval and handoff payloads, and raw model output. This is not the Monitor: `/monitor` and `/api/v1/monitor/summary` remain behind a separate HTTP Basic operator credential, and a `ds_live_…` key cannot authenticate either one.

## Response `200`

Operational projection. `data.status` and every `data.<section>.status` is one of ok, attention, degraded, or unavailable; `data.attention` lists the concrete reasons and `data.freshness` the per-section timestamps.

## Other responses

- `401`: A read-scoped API key is required
- `403`: The key does not grant read access
- `429`: Request quota exceeded

---

[API](https://skmtc.dev/daystruct/apis/daystruct-api.md) · [All operations](https://skmtc.dev/daystruct/apis/daystruct-api/llms.txt) · [OpenAPI document](https://skmtc.dev/daystruct/apis/daystruct-api/revisions/8cd3c7f60e18?raw)