Operations
Client Ops API
Client Ops API is now published behind ISAAC www on Vercel so developers can consume a stable OpenAPI contract without direct BFF host coupling.
Published endpoints
OpenAPI JSON (Vercel): /api/client-ops/openapi
Client Ops routes: /api/client-ops/jobs, /jobs/{job_id}, /jobs/{job_id}/events, /jobs/{job_id}/artifacts, /jobs/{job_id}/cancel, /usage
Authentication and tenancy
All Client Ops routes require X-Client-API-Key tied to a tenant-scoped key record.
Prod execution remains permission-gated and quota-limited; usage endpoint provides tenant-level metering visibility.
Recommended integration path
Point SDK generation and contract checks to the Vercel OpenAPI endpoint for stable discovery.
Do not integrate against direct BFF docs/openapi paths; they are internal transport and may be blocked.
Use job status response triage fields (`failure_code`, `severity`, `next_action`, `envelope_path`) for deterministic retry/repair logic.