Skip to main content
When an agent payment exceeds its approval threshold (or a policy rule flags it), it waits in the approvals queue for a human decision. See Approvals for the concept overview.

​
List pending approvals

GET /v1/approvals/pending
Returns payments awaiting a decision. Each item includes the agent, amount, recipient, the agent’s stated purpose, budget context, which rules flagged it (flaggedByRuleTypes), and expiresAt — the end of the human decision window.

​
List completed approvals

GET /v1/approvals/completed
Returns resolved requests with their resolution:
ResolutionMeaning
approvedApproved and settled
executingApproved — transfer currently in flight
deniedDenied by a human
failedApproved but execution failed
expiredNo decision within the window

​
Approve

POST /v1/approvals/:id/approve
No body. For wallet payments, Reinx executes the transfer immediately on approval.

​
Deny

POST /v1/approvals/:id/deny

{ "feedback": "Duplicate subscription — we already pay for this on the design agent." }
feedback is required (1–1,000 characters) — it’s delivered to the agent via the get_denial_feedback MCP tool so it can adjust before retrying.
Approving and denying are deliberately quick actions — no step-up re-verification — because each one releases a single, already-policy-validated payment with a fixed amount and recipient.