Bernstein Missions API

The Missions API from Bernstein — 8 operation(s) for missions.

Operations 8

GET /missions Missions List #
GET /missions/{mission_id} Mission Projection #
GET /missions/{mission_id}/digest Mission Digest #
GET /missions/{mission_id}/evidence/{task_id} Mission Evidence #
GET /api/v1/missions Missions List #
GET /api/v1/missions/{mission_id} Mission Projection #
GET /api/v1/missions/{mission_id}/digest Mission Digest #
GET /api/v1/missions/{mission_id}/evidence/{task_id} Mission Evidence #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/bernstein-run:bernstein-run-missions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

bernstein-run-missions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Bernstein Task Server Missions API
  description: 'Bernstein REST API - the open-source governance layer for AI agents, one git worktree per task.


    ## Authentication


    Authentication is ENABLED by default. Include a Bearer token in all requests:


    ```

    Authorization: Bearer

    ```


    To run without auth (development only), set `BERNSTEIN_AUTH_DISABLED=1` - this logs a loud warning and passes every request through.


    Public endpoints (no auth required): `/health`, `/health/ready`, `/health/live`, `/ready`, `/alive`, `/.well-known/agent.json`, `/docs`, `/openapi.json`, and the auth-flow endpoints (`/auth/login`, `/auth/oidc/callback`, etc.).


    Webhook and hook endpoints (`/webhook`, `/webhooks/*`, `/hooks/{session_id}`) authenticate via HMAC-SHA256 signatures - they do NOT accept Bearer tokens.


    ## Base URL


    Default: `http://127.0.0.1:8052`. Override with env vars `BERNSTEIN_HOST` and `BERNSTEIN_PORT`.


    ## Error Format


    All errors return JSON with a `detail` field:


    ```json

    {"detail": "Task not found: task-xyz"}

    ```


    | Status | Meaning |

    |--------|---------|

    | 400 | Bad request (validation error) |

    | 401 | Unauthorized (missing/invalid token) |

    | 403 | Forbidden (IP not in allowlist) |

    | 404 | Resource not found |

    | 409 | Conflict (task already in terminal state) |

    | 429 | Rate limited - respect the `Retry-After` header |

    | 500 | Internal server error |'
  version: 3.22.0
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0
  contact:
    name: Alex Chernysh
    url: https://github.com/sipyourdrink-ltd/bernstein
servers:
- url: http://{host}:{port}
  description: Task server started by the Bernstein CLI on the operator's own machine. There is no hosted instance; substitute the host and port of your install.
  variables:
    host:
      default: 127.0.0.1
      description: Interface the task server binds to. Loopback by default.
    port:
      default: '8052'
      description: Task server port. Override with BERNSTEIN_PORT.
tags:
- name: Missions
paths:
  /missions:
    get:
      summary: Missions List
      description: List mission ids that have a ledger to project, newest first.
      operationId: missions_list_missions_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Missions
  /missions/{mission_id}:
    get:
      summary: Mission Projection
      description: 'Serve the mission projection receipt for ``mission_id``.


        The response is a deterministic function of the mission''s ledger file: the

        same ledger bytes serve the same ``status`` and ``mission_status_hash`` from

        any server, so two operators cross-check byte for byte.

        ``ledger_verified=false`` (with ``overall=unverified``) marks a chain that no

        longer recomputes -- the timeline still renders, but the screen must show the

        unverified banner instead of trusting the state.'
      operationId: mission_projection_missions__mission_id__get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
  /missions/{mission_id}/digest:
    get:
      summary: Mission Digest
      description: 'Serve the canonical daily progress digest for a fire instant.


        Read-only: the digest is recomputed from the ledger as a pure fold, so the

        endpoint never writes to the chain. The payload carries the ``digest_hash``,

        the ``receipt_id`` (the per-fire delivery idempotency key), and the verbatim

        ``message`` the digest projects to -- the exact bytes a chat delivery posts,

        so a caller can cross-check a posted message against this projection.'
      operationId: mission_digest_missions__mission_id__digest_get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      - name: fire_time
        in: query
        required: true
        schema:
          type: integer
          description: Integer Unix epoch of the canonical fire instant.
          title: Fire Time
        description: Integer Unix epoch of the canonical fire instant.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
  /missions/{mission_id}/evidence/{task_id}:
    get:
      summary: Mission Evidence
      description: 'Serve the sealed evidence bundle behind a timeline element''s provenance link.


        ``bundle_hash`` is recomputed from the canonical binding bytes on every read,

        so the drawer always shows the bundle''s current identity -- and a bundle that

        no longer matches the hash a phase receipt bound projects that phase as

        unverified in the mission projection above.'
      operationId: mission_evidence_missions__mission_id__evidence__task_id__get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      - name: task_id
        in: path
        required: true
        schema:
          type: string
          title: Task Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
  /api/v1/missions:
    get:
      summary: Missions List
      description: List mission ids that have a ledger to project, newest first.
      operationId: missions_list_api_v1_missions_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - Missions
  /api/v1/missions/{mission_id}:
    get:
      summary: Mission Projection
      description: 'Serve the mission projection receipt for ``mission_id``.


        The response is a deterministic function of the mission''s ledger file: the

        same ledger bytes serve the same ``status`` and ``mission_status_hash`` from

        any server, so two operators cross-check byte for byte.

        ``ledger_verified=false`` (with ``overall=unverified``) marks a chain that no

        longer recomputes -- the timeline still renders, but the screen must show the

        unverified banner instead of trusting the state.'
      operationId: mission_projection_api_v1_missions__mission_id__get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
  /api/v1/missions/{mission_id}/digest:
    get:
      summary: Mission Digest
      description: 'Serve the canonical daily progress digest for a fire instant.


        Read-only: the digest is recomputed from the ledger as a pure fold, so the

        endpoint never writes to the chain. The payload carries the ``digest_hash``,

        the ``receipt_id`` (the per-fire delivery idempotency key), and the verbatim

        ``message`` the digest projects to -- the exact bytes a chat delivery posts,

        so a caller can cross-check a posted message against this projection.'
      operationId: mission_digest_api_v1_missions__mission_id__digest_get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      - name: fire_time
        in: query
        required: true
        schema:
          type: integer
          description: Integer Unix epoch of the canonical fire instant.
          title: Fire Time
        description: Integer Unix epoch of the canonical fire instant.
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
  /api/v1/missions/{mission_id}/evidence/{task_id}:
    get:
      summary: Mission Evidence
      description: 'Serve the sealed evidence bundle behind a timeline element''s provenance link.


        ``bundle_hash`` is recomputed from the canonical binding bytes on every read,

        so the drawer always shows the bundle''s current identity -- and a bundle that

        no longer matches the hash a phase receipt bound projects that phase as

        unverified in the mission projection above.'
      operationId: mission_evidence_api_v1_missions__mission_id__evidence__task_id__get
      parameters:
      - name: mission_id
        in: path
        required: true
        schema:
          type: string
          title: Mission Id
      - name: task_id
        in: path
        required: true
        schema:
          type: string
          title: Task Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
      tags:
      - Missions
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
      - loc
      - msg
      - type
      title: ValidationError