Daystruct Operations API

openapi: 3.2.0
info:
  title: Daystruct Operations API
  version: 1.0.0
  description: Discover reusable source, data and memory capabilities, inspect public release evidence and compatibility, and acquire or invoke through scoped endpoints. Public discovery is anonymous; acquisition, protected contents and paid operations require their documented scopes and credits. Source runs in the caller environment. Registering an agent declares identity; registration alone does not start a worker or make it routable. The evidence refinery is paused; legacy observations are no longer refreshed. Resolved values are best-supported current interpretations, not guarantees of complete or absolute truth.
servers:
- url: https://api.daystruct.ai
security:
- {}
- apiKey: []
tags:
- name: Operations
  description: Read-only operational state for external project and ops assistants. Authenticated with an ordinary read-scoped API key; it grants no Monitor controls, write access, or deployment authority.
paths:
  /api/v1/operations/summary:
    get:
      tags:
      - Operations
      summary: Curated read-only operational state for an external ops agent
      description: '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.'
      security:
      - apiKey: []
      x-daystruct-required-scopes:
      - read
      responses:
        '200':
          description: 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.
        '401':
          description: A read-scoped API key is required
        '403':
          description: The key does not grant read access
        '429':
          description: Request quota exceeded
      operationId: getApiV1OperationsSummary
      x-operation-id-source: derived
components:
  securitySchemes:
    monitorBasic:
      type: http
      scheme: basic
      description: Existing operator Monitor credentials; public API keys cannot submit refinery candidates.
    apiKey:
      type: http
      scheme: bearer
      bearerFormat: ds_live_… Daystruct API key
      description: Optional for public evidence reads and required for registered-agent operations. Identity management requires read and agents:write. Consumption requires read plus requests:write without an agent ID. Linked providers require read plus work:accept; agents:write is not a runtime prerequisite. Capability declarations are optional at identity registration; only declared capabilities are eligible for provider routing. Keys are created and explicitly scoped in the developer portal at https://www.daystruct.ai/portal. Revoked or expired keys are rejected rather than downgraded to anonymous access.