Skip to content

Route index

Every route in the spec of the release api.felix.run runs, one line each. A route a guide explains links to that section; the rest link to their operation in the OpenAPI explorer, which has the request schema and a request builder but not the response shape — every harness route returns a plain object, so the spec cannot describe one. The REST API and Management API guides are where those shapes are written down.

178 routes, 141 of them explained in a guide.

System

  • GET /.well-known/agent-card.jsonAgent CardREST API, Well-known
  • GET /.well-known/jwks.jsonJWKSREST API, Well-known
  • GET /healthLiveness — {"status":"ok","env":…,"version":…,"multi_region":false,"federation":null}REST API, System
  • GET /liveLiveness, named for what it is — the same static body as /health, no I/OREST API, System
  • GET /metricsPrometheus text exposition.REST API, System
  • GET /readyReadiness. Probes the dependencies and answers 503 when one is down, so a pod with a dead database leaves rotation instead of being restartedREST API, System

A2A

Approvals

Artifacts

Audit

Auth

Threads

Repos

Documents

Eval

Files

Internal

Jobs

Manifests

MCP

Memory

Plans

Push

Skill library

Skills

  • GET /skills/{manifest_name}Every skill this manifest can reach, and which are currently active.Management API, Skills
  • GET /skills/{manifest_name}/activations/recentWhich skill activated on which turn, newest first.Management API, Skills
  • GET /skills/{manifest_name}/{skill_name}One skill, including the instructions `activate_skill` would return.Management API, Skills

Triggers

Usage

OpenAI

Workflows

  • GET /workflowsThe tenant's workflows, most recently saved first, without their definitions.Management API, Workflows
  • POST /workflows/-/checkPorts and problems for a definition, without saving it — what the editor shows as you wire.Management API, Workflows
  • GET /workflows/-/kindsThe step kinds a workflow can use: built in, and any a plugin registered.Management API, Workflows
  • GET /workflows/-/toolsThe tools a `tool_call` step naming `manifest` can call, with their input schemas.Management API, Workflows
  • DELETE /workflows/{workflow_id}Delete a workflow; with `If-Match`, only that revision.Management API, Workflows
  • GET /workflows/{workflow_id}Get WorkflowManagement API, Workflows
  • PUT /workflows/{workflow_id}Save a definition whole. `201` when this created it, `200` when it replaced one.Management API, Workflows
  • GET /workflows/{workflow_id}/runsThe workflow's runs, newest first, each with its steps' statuses.Management API, Workflows
  • POST /workflows/{workflow_id}/runsStart a run of the workflow's current revision with `inputs`.Management API, Workflows
  • GET /workflows/{workflow_id}/runs/{run_id}Get RunManagement API, Workflows
  • POST /workflows/{workflow_id}/runs/{run_id}/cancelAsk the run to stop: `cancelling` until the orchestrator aborts what is in flight.Management API, Workflows
  • GET /workflows/{workflow_id}/runs/{run_id}/steps/{step_id}/threadThe transcript of one step's child run: the snapshot `GET /chat/sessions/{id}` answers.Management API, Workflows
  • GET /workflows/{workflow_id}/runs/{run_id}/streamThe run as it changes: a `workflow_run` frame for each new version, then `[DONE]` once over.Management API, Workflows