POINTCAST STANDARDS · NO. 4 · DRAFT · 2026-10-05

Agent Receipts

First principle: An agent that acts for someone should leave a signed receipt the operator can audit.

When Grok Bot pulls the rope, calls the marine layer, or files a price, Mike should be able to see a receipt: what ran, when, with which inputs, and what came back. Receipts are for audit, not for payment — though they can sit beside x402 payment receipts when money does move.

A receipt names the agent, the operator, the action, a timestamp, and optional passport hash. L0 is an unsigned log; L1 is key-signed (Devnet chain_submit_signed or EIP-712); L2 adds operator cosign; L3 anchors onchain. No required staking.

PointCast already countersigns some clerk and x402 flows. This standard generalizes the shape to everyday agent acts — sky calls, rope pulls, drum taps, yard chores — so an operator can reconstruct a day.

Machine line on Devnet: receipt: v=0.1 …. Full schema notes are in the spec.

Machine spec: /standards/agent-receipts/spec.md · Series: /standards/ · Related: No. 1 Agent Passport.