Fleet and Operations API
Every endpoint on this page requires the operations bearer token. These are control-plane APIs; call them from a trusted server, CLI, or automation rather than a browser.Fleet execution
repos (optional repository-name array), limit, threshold, engine, and legacy modal. An omitted or empty repos array requests auto-planning. A non-empty selection that resolves to no repositories is rejected instead of widening into an auto-planned fleet run. @profile entries require FL_CONFIG.md in the API runtime; use explicit repository names for the standard Railway image. The exact operation payload varies by engine; inspect status before issuing another run.
The API service must have INNGEST_BASE_URL, INNGEST_EVENT_KEY, and INNGEST_SIGNING_KEY configured for the same Inngest service as the fleet worker. Without that connection, run requests fail closed with 503.
Plan and status reads are proxied server-to-server to the stateful worker.
Configure FLEET_WORKER_BASE_URL on fl-api and the same server-only
FLEET_STATUS_TOKEN on fl-api and fl-fleet. Without both, these reads return
503; they never substitute the stateless API container’s empty local data.
Quality, audit, and discovery
Benchmarks
List endpoints return
{items, total}. Task details are the stored benchmark record.