Skip to content

Approvals

Every operation has an approval level (x-prudai-approval in the spec). It is in the reference with every operation. Reading never asks for approval. When an agent writes, a person looks along, unless the level says otherwise.

Measured on 8 November 2026.

ProductStateHow the approved call comes back
LEO familyIn production, for the writes that exist there: deleting and restoring conversations. Knowledge bases are coming soon.The same call with the header x-prudai-approval: <approval-id>
IRMAEnforced per organisation for which the gate is switched on.The same call with the header X-Prudai-Approval-Grant
ORDOIn production. The approval gate can be set per organisation: off, shadow (record) or enforce.POST /v1/approvals/{id}/execute

none

No extra step. Reading, or computing without storing anything.

instruct

Not blocking. The agent states its intent.

confirm

The user confirms exactly this call. Default for POST, PUT and PATCH.

review

A second person or role approves. Default for DELETE.

forbidden_for_agents

Never by an agent, only by a person in the app. The answer stays 403 forbidden_for_agents, even with an approval.

  1. The call without approval runs nothing and answers 202:

    {
    "approvalRequest": {
    "id": "apr_...",
    "level": "confirm",
    "operation": "...",
    "method": "POST",
    "path": "...",
    "args_hash": "...",
    "expires_at": "...",
    "approval_url": "..."
    }
    }
  2. A person decides in the Prudai Console, under Approvals. An agent or key cannot approve itself. With review that is an administrator, with a reason.

  3. The caller repeats the same call with the header:

    x-prudai-approval: apr_...

The server runs exactly the approved call: args_hash is the hash of operation, path, query and body. A changed body, another route or a second use is refused. A request stays open for 15 minutes; an approval is then valid for 10 minutes and works once.

With ?dryRun=true you see what would happen, without approval and without storing anything. Every request, decision and execution goes into the audit trail.

  • CLI: a write that waits gives exit 2 and the approval link. prudai approvals wait <id> --product <product> --execute waits for the decision and then runs. The CLI never approves by itself. See CLI.
  • MCP: execute_tool returns approval_required. See MCP.
  • Anything with costs or payment waits for a person. An agent never transfers money by itself.