Skip to content
AX Framework
Feedback pattern

Action Receipts

Return a durable, verifiable record of every state-changing action.

Problem

Agents report success to people based on whatever the product returned. When that response is a redirect or a toast, there is no evidence to check and nothing to reference later.

Context

Use this pattern when:

  • Actions create or change something a person cares about: orders, bookings, messages, settings.
  • People, agents, or support staff may need to verify what happened afterward.

Recommended solution

Return a receipt for every state-changing action: a durable record with an ID, the action name, the exact inputs applied, the resources affected, the actor and grant used, and a timestamp. Store receipts so they can be retrieved later.

  1. 01Generate a receipt inside the same transaction as the action.
  2. 02Include resources affected and amounts charged.
  3. 03Record the agent and the person it acted for.
  4. 04Make receipts retrievable by ID.

Interaction diagram

Interaction diagram for Action Receipts. 1. AI agent to Product · AX layer: create_booking(…). 2. Product · AX layer to AI agent: receipt rcpt_77a1. 3. AI agent to Person: Booked. Ref BK-55210. 4. Person to Product · AX layer: GET /receipts/rcpt_77a1.PersonAI agentProduct · AX layercreate_booking(…)1receipt rcpt_77a12Booked. Ref BK-552103GET /receipts/rcpt_77a14
request response internal step

Example implementation

Illustrative example

Examples use a fictional store and illustrative field names. Adapt the shape to your stack; the qualities matter more than the exact format.

Receiptjson
{
  "id": "rcpt_77a1",
  "action": "create_booking",
  "status": "completed",
  "occurredAt": "2026-10-06T14:03:52Z",
  "actor": { "agent": "assistant.example", "onBehalfOf": "user_2291", "grant": "grt_41c" },
  "effects": [
    { "type": "created", "resource": "/bookings/BK-55210" },
    { "type": "charged", "amount": 412.00, "currency": "USD", "paymentId": "pay_19c" }
  ]
}

Accessibility and security

Accessibility

  • Send people a human-readable version of the receipt through their preferred channel.

Security

  • Receipts can contain personal data; apply the same access controls as the underlying resources.
  • Make receipts append-only so they serve as an audit trail.

Applies the principles Verifiable Outcomes and Human Oversight.