The whole orchestration surface is deprecated, and every route on it keeps
answering. It drives the legacy orchestration runtime, which is FROZEN — it accepts no new capabilities. The durable runtime enforces policy at the tool boundary, not only at the gateway, and it is the only runtime new work is built on.Nothing here is removed and no response shape changes. The announcement is carried
in response headers only — Deprecation (RFC 9745),
Link rel="deprecation", Warning: 299, X-Naive-Deprecation-Id and, for a
{kind:"use"} row, X-Naive-Replacement. There is no Sunset header on any of
them: every row is frozen, and a Sunset would be a date the platform has not
promised.Announced 2026-07-29. The freeze ends when
company_containers with provider='hermes' and status='running' reaches zero — not on a date.Two things on this page are NOT deprecated. POST /v1/cron/reconcile-*,
POST /v1/cron/drain-events and POST /v1/cron/process-conversions are
shared-secret platform reconcilers that merely share the /v1/cron prefix; and
the sidecar control API described in API Overview is
the wire the legacy runtime is driven over, which stays frozen rather than
deprecated.Replacement surface: the durable runtime API. Endpoint Groups
CEO Agent
There is no bare /v1/ceo mount. The lead-agent router is mounted at
/v1/companies/{id}/ceo/* and /v1/users/{user_id}/ceo/* only — the same router,
reached through either subject. Both spellings are published in the OpenAPI spec,
so the interactive “Endpoints” section addresses the routes that answer.
Tasks
Objectives
Employees
Cron Jobs
Memory
Authentication
All endpoints require either a session cookie or a Bearer API key:
CEO endpoints use the company-scoped path (/v1/companies/:companyId/ceo/*). All other orchestration endpoints resolve the company from the API key or session automatically.
