/api/v2/ops/admin/*) give a platform API key the operator’s view of the deployment. An External App is refused with 403, even when it holds the permission. Each write takes an Idempotency-Key. Every route is reachable from MCP through forge_call_operation in the observe tool group.
Attention and notes
- List the attention board: failed and stuck runs, pending approvals, invalid credentials and the other signals the Console’s Ops page shows, most severe first. Needs
workflows:readat platform scope. - Acknowledge an attention item so it leaves the active board until the acknowledgment expires, 24 hours by default. Needs
platform:manage. The acknowledgment records the key as the one who acknowledged it. - Add an investigation note to a run, an agent or another resource, and list a resource’s notes, newest first. Adding needs
audit:read; listing needsworkflows:read. A note records the key as its author, and the list does not answer who wrote a note. Note text is masked like run content.
Run audit
- List a run’s audit events, newest first, and read its audit packet: its disposition, approvals, governance decisions, key events and recommended actions. Both need
workflows:readat the run’s home. A run that does not exist, or one homed where the key does not hold the permission, answers404. - Events about people are included only when the key also holds
workforce:read. A key reads no source-restricted knowledge, so knowledge events keep only what anyone may read.
Workflow analytics
- Read the workflow performance and reliability overviews for a time window, list recently failed runs, and list the slowest steps. Each needs
workflows:readat platform scope.
Not on these routes
Alert rules, traces, span detail, the Events stream and turn outcomes stay in the Console: their authoring runs as a person and their reads join raw tool and model content. Machines subscribe to webhooks and readGET /api/v3/events, runs/listEvents and compliance/export/audit instead. A person’s own notification inbox has no equivalent for a key.
