emisar API

openapi: 3.1.0
info:
  title: emisar API
  version: '2026-11-06'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-11-06: 8 operation(s) read from 17 public documentation page(s) (each operation
    names its page in x-source). This is not the provider''s published contract; emisar has published no machine-readable contract that the pipeline
    could find. Engine: local.'
  x-evidence-tiers:
    code-example: 3
    documentation: 5
    pages-with-code: 14
    pages-read: 17
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-11-06'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://emisar.dev/docs/mcp-reference
  - https://emisar.dev/docs/quickstart
  - https://emisar.dev/docs/runner-cli
  - https://emisar.dev/docs/bridge-upgrades
  - https://emisar.dev/docs/connect-cli-agent
  - https://emisar.dev/docs/investigate-a-service
  - https://emisar.dev/docs/host-install
  - https://emisar.dev/docs/containers
  - https://emisar.dev/docs/autoscaling-fleets
  - https://emisar.dev/docs/network-requirements
  - https://emisar.dev/docs/runner-fleet
  - https://emisar.dev/docs/publishing-packs
  - https://emisar.dev/docs/pack-registry
  - https://emisar.dev/docs/credentials
  - https://emisar.dev/docs/signed-dispatch
  - https://emisar.dev/docs/audit-and-siem
  - https://emisar.dev/docs/security-model
servers:
- url: https://packs.acme.internal
paths:
  /:
    get:
      operationId: get
      tags:
      - Api
      summary: GET /
      x-source: https://emisar.dev/docs/investigate-a-service
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -sI http://localhost:8080 | head -1 \n You should see HTTP/1.1 200 OK . The runner also needs access to the Docker\n daemon.\
          \ Add its user to the docker group and restart the runner, as the\n docker pack's setup describes:\n shell \n sudo usermod -aG docker\
          \ emisar\nsudo systemctl restart emisar \n Docker access is root access \n Anything in the docker group can control the host through\
          \ Docker. Do this"
  /api/audit:
    get:
      operationId: get_api_audit
      tags:
      - Api
      summary: Reads GET /api/audit for this account.
      x-source: https://emisar.dev/docs/credentials
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /api/mcp/rpc:
    post:
      operationId: post_api_mcp_rpc
      tags:
      - Api
      summary: POST /api/mcp/rpc
      x-source: https://emisar.dev/docs/mcp-reference
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PostApiMcpRpcRequest'
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -X POST https://emisar.dev/api/mcp/rpc  -H \"Authorization: Bearer $EMISAR_API_KEY\"  -H \"Content-Type: application/json\"\
          \  -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"tools/list\"}' \n Use MCP tools from the shell \n The MCP bridge also exposes all\
          \ tools as a CLI. This lets any LLM use emisar in\n scripts too, without the usual limits of the MCP protocol.\n Authenticate once,\
          \ with emisar-mcp auth \n or dur"
  /install-mcp.sh:
    get:
      operationId: get_install_mcp_sh
      tags:
      - Install Mcp
      summary: Install the MCP bridge
      x-source: https://emisar.dev/docs/quickstart
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /install.sh:
    get:
      operationId: get_install_sh
      tags:
      - Install
      summary: Install the runner
      x-source: https://emisar.dev/docs/quickstart
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /runner/register:
    post:
      operationId: post_runner_register
      tags:
      - Runner
      summary: Exchanges the enrollment key for this runner's own token
      description: Outbound HTTPS POST to /runner/register on the emisar origin (https://emisar.dev) to exchange the enrollment key for the runner's
        token. First connect, and again after an enrollment-key change.
      x-source: https://emisar.dev/docs/network-requirements
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /runner/token/refresh:
    post:
      operationId: post_runner_token_refresh
      tags:
      - Runner
      summary: Swaps the runner's token for a successor before the old one expires
      description: Outbound HTTPS POST to /runner/token/refresh on the emisar origin (https://emisar.dev) to refresh the runner's token. Occurs
        on the next connect after its token is 60 days old.
      x-source: https://emisar.dev/docs/network-requirements
      responses:
        '201':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v1/catalog.json:
    get:
      operationId: get_v1_catalog_json
      tags:
      - Catalog
      summary: GET /v1/catalog.json
      x-source: https://emisar.dev/docs/pack-registry
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -fsS https://packs.acme.internal/v1/catalog.json -o current.json\npackctl catalog build --packs ./packs --out ./dist  --base-url\
          \ https://packs.acme.internal  --repo-url https://github.com/acme/ops-packs --previous current.json \n What your registry changes #\
          \ \n emisar works unchanged. \n Runners advertise installed packs no matter where they came from, and trust,\n policy, approvals, and\
          \ audit tre"
components:
  schemas:
    PostApiMcpRpcRequest:
      type: object
      properties:
        jsonrpc:
          type: string
        id:
          type: integer
        method:
          type: string
  securitySchemes:
    bearer:
      type: http
      scheme: bearer
security:
- bearer: []
tags:
- name: Api
- name: Catalog
- name: Install
- name: Install Mcp
- name: Runner