Pending approvals
Approve and reject accept
{"reason": "…"}. The reason reaches the agent on a rejection and the audit record either way.
A pending entry carries the statement as it will run, the agent’s stated reason, class and verb, resources, hazards, whether it is bounded, the estimated records, the deadline, its preview, and the fence protecting it.
Debug sessions
Start with
{"connection":"shop","classes":["write"],"unbounded_only":false,"agents":["agent:support"],"ttl_minutes":30}. Stopping refuses whatever is still waiting. See Debug Mode.
Leases
Revocation is a review capability on purpose: severing access mid-incident is what a reviewer is on call to do.
Agents
Listing an agent shows its breaker state, signal counts, and why it was frozen. Reinstating requires a reason, which is recorded — that judgement is the most useful thing in the record when the same agent trips again next week.
Revoking a lease severs the current credential; it does not lock the agent out, because a lease is not an authentication credential. To stop an agent entirely, freeze it and revoke its leases.
Connections
A connection summary includes its engine, health, policy mode, posture, and the capability ladder — the page a security reviewer reads, in the same terms the CLI prints.
Audit
Filters:
agent, task, type, effect, outcome, limit, after. Verify returns HTTP 409 when the chain is broken. See audit.
Events
GET /api/v1/events (read) is a server-sent event stream of paused and resolved notifications, which is what makes the operator view live.
It is one-directional — every action goes back over an ordinary POST — so SSE carries the same Authorization header as everything else and needs no second authentication path. A subscriber that connects mid-session is sent everything already pending first. A subscriber that falls behind loses events rather than stalling the gateway: a live view missing a frame is survivable, a browser holding up every agent’s database access is not.
Health
GET /health is unauthenticated. It reports that the process is up and how many connections are configured, and nothing about what it governs.