> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nasiko.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Server-Sent Events stream of `{"status": ..., "build_id": ...}` on each

> Server-Sent Events stream of `{"status": ..., "build_id": ...}` on each
status change, polling every 3s until the build reaches `success`/`failed`
(or `{"status": "not_found"}` once, if the build id doesn't exist).
Callers below deployer role get `200 {"available": false}` instead.



## OpenAPI

````yaml /api-reference/openapi.json get /api/agents/deploys/{build_id}/stream
openapi: 3.1.0
info:
  title: Nasiko API
  description: >-
    HTTP API for the Nasiko OpenRuntime: agents, coding harnesses, TokenOps,
    routing, MCP, and secrets. Spec is generated from annotated routes; some
    surfaces are documented on the hand-written pages alongside this file.
  license:
    name: ''
  version: 0.1.0
servers: []
security: []
tags:
  - name: secrets
    description: Encrypted per-user agent secrets
  - name: catalog
    description: >-
      Agent catalog: registration, discovery, versions, per-agent secrets, and
      source import
  - name: agents
    description: >-
      Agent lifecycle: deployments, LLM routing config, update/rollback,
      upload-and-deploy
  - name: orchestrator
    description: >-
      A2A dispatch: routing-engine/ReAct orchestrator and direct agent chat,
      plus routing stats
  - name: users
    description: >-
      User management: CRUD, roles, credentials, accessible agents
      (superuser-only)
  - name: usage
    description: Per-user token usage and cost reporting
  - name: observability
    description: Sessions, traces, spans, agent logs, and FinOps reporting
  - name: llm-router
    description: LLM routing presets, provider/model catalog, and tier→model registry
  - name: mcp
    description: >-
      MCP gateway: agent-facing JSON-RPC tool calls, connector
      registration/upload/sharing, credentials & OAuth, and per-agent tool
      permissions
paths:
  /api/agents/deploys/{build_id}/stream:
    get:
      tags:
        - agents
      summary: 'Server-Sent Events stream of `{"status": ..., "build_id": ...}` on each'
      description: >-
        Server-Sent Events stream of `{"status": ..., "build_id": ...}` on each

        status change, polling every 3s until the build reaches
        `success`/`failed`

        (or `{"status": "not_found"}` once, if the build id doesn't exist).

        Callers below deployer role get `200 {"available": false}` instead.
      operationId: deploy_status_sse
      parameters:
        - name: build_id
          in: path
          description: Build id
          required: true
          schema:
            type: string
            format: uuid
      responses:
        '200':
          description: >-
            `text/event-stream` of build status updates, or `{"available":
            false}`
          content:
            text/event-stream: {}

````