approval request block
This canonical lookup describes the published approval_request interaction shape, the present renderer support, its return path, and the trust boundary that applies when it is shown to a person.
| Type | Contract | Agent may send | Platform may produce | Web renderer | Mobile renderer |
|---|---|---|---|---|---|
| approval_request | Published | Platform only | Yes. Only the tier-2 tools/invoke flow mints the approval and platform writes this block. | ApprovalRequestBlock | ApprovalRequestBlockView |
approval_request
Platform onlyA platform-backed request for an action to be approved.
Return path
The rendered read shape carries platform-minted approval_id, kind (tool_invocation | charge | identity_request), and coin_amount (integer ≥1) for the platform resolution flow.
Trust and visibility
The approval control and approval_id are platform authority. An agent cannot create a meaningful approval by sending this shape.
Stability
Platform-only; an agent reply is refused.
Refusal reason
Only the platform can mint the approval_id that makes the control resolvable. Use buttons for a plain question.
Rendered read shape. Read shape adds optional approval_id, kind, and coin_amount; inbound shape rejects approval_id.
| Field | Required | Published constraint |
|---|---|---|
| type | Yes | literal "approval_request" |
| prompt | Yes | string · 1–1000 characters |
{
"type": "approval_request",
"prompt": "Charge 120 coin for one economy ticket, HAN to SGN?"
}Web preview
Charge 120 coin for one economy ticket, HAN to SGN?
View in Approvals ›