Public Receipts API
Every recorded, non-simulated authorization or purchase decision has an opaque public receipt id. The id has the form rcpt_ followed by 32 lowercase hexadecimal characters. It does not contain a tenant, agent, decision, rail, or timestamp.
Status: Live in the sandbox staging environment at https://staging-app.robotmoney.com/r/{receipt_id} and https://staging-api.robotmoney.com/v1/receipts/{receipt_id}.json. The production host https://receipts.robotmoney.com is Planned until the production promote completes.
The public receipt page is:
https://receipts.robotmoney.com/r/{receipt_id}The canonical JSON endpoint is:
GET https://api.robotmoney.com/v1/receipts/{receipt_id}.jsonNo authentication is required. GET /v1/receipts/{receipt_id} returns the same JSON by default. It may return a small HTML view when the request accepts text/html.
Signed Response
The response contains summary, signature, jwks_url, verify_url, and receipt_url. signature is a compact JWS with type robotmoney-decision+jws. Its payload is exactly summary. The signed summary contains the receipt id, never an internal authorization or purchase id.
Use jwks_url to load the current public signing keys. Verify the compact JWS, require the expected type, then compare its payload with summary. verify_url is the canonical signed JSON URL for the receipt.
{
"schema_version": 1,
"receipt_id": "rcpt_0123456789abcdef0123456789abcdef",
"kind": "authorization",
"visibility": "full",
"status": "settled",
"activity_url": "https://app.robotmoney.com/activity/evt_...",
"summary": {
"receipt_id": "rcpt_0123456789abcdef0123456789abcdef",
"decision": "approved",
"status": "settled",
"amount": "10.00000000",
"currency": "USDC",
"created_at": "2026-11-01T12:00:00.000Z",
"expires_at": "2026-11-02T12:00:00.000Z"
},
"sections": {
"memory": { "visibility": "shown", "context": {} },
"intelligence": { "visibility": "shown", "decision": "approved" },
"control": { "visibility": "shown", "checks": [] },
"accounts": { "visibility": "shown", "timeline": [], "events": [] },
"proof": { "visibility": "shown", "anchor_status": "anchored" }
},
"signature": "compact-jws",
"jwks_url": "https://auth.robotmoney.com/.well-known/jwks.json",
"verify_url": "https://api.robotmoney.com/v1/receipts/rcpt_0123456789abcdef0123456789abcdef.json",
"receipt_url": "https://receipts.robotmoney.com/r/rcpt_0123456789abcdef0123456789abcdef"
}All timestamps are UTC ISO 8601 strings. Amounts are decimal strings.
The Five Sections
Memory
For a full authorization receipt, sections.memory.context is the bounded payment context captured before that decision. It can include prior decision counts, recent amount aggregates, review counts, execution counts, the last policy version, and whether this was the first decision for the agent and payee. Purchase receipts currently return context: null with availability: not_recorded_for_purchase.
Intelligence
For a full authorization receipt, Intelligence shows the stored decision, reason code, policy version, and matched public rule text. It never exposes the internal policy id. Purchase receipts show their stored decision and reason code.
Control
For a full authorization receipt, Control shows the bounded gate check names, ordinals, statuses, expiry, and stored review outcome. It never exposes reviewer identity or review reason text.
Accounts
Accounts shows amount, currency, public status, and a compatibility timeline array. Full receipts can also show the public counterparty, memo, and verified settlement evidence.
Recorded authorizations become expired after their stored expiry according to database server time. Submitted, failed, and settled states take precedence. Decision-only approvals also state that RobotMoney did not move money. Reviewed approval checks retain their decision-time status and carry the label Required at decision, granted by review.
The bounded events array is the server-built activity view. It is capped at 16 rows and remains in event order. Each event contains sentence, actor, role, and at. An event can also contain id, tx_hash, block, or batch. Minimal receipts retain only the generic decision, submission, settlement, hashed, and anchored events. Their actor is hidden_by_owner.
The top-level activity_url links to the authenticated Console activity view for the selected decision audit event. It is navigation for an authorized Console user. It is not a public tenant data lookup endpoint.
Proof
Proof always shows the verified audit record hash and its previous hash. A database-only tenant reports database_hash_chain. An on-chain tenant reports anchor_pending until a containing anchor is confirmed. A confirmed anchor reports anchored with the Merkle root, inclusion proof, transaction hash, block, contract, and chain.
New tenants start with the database hash-chain guarantee. A platform operator can promote eligible paid and pilot tenants to Base Sepolia anchoring. Base mainnet remains fenced. Promotion never causes a receipt to claim an anchor until a confirmed containing transaction exists.
Settlement and anchoring are based on verified persisted state. A provider success response alone never creates a settled event or an anchored claim.
Receipt Visibility
Tenant owners control public detail with receipt_visibility:
fullshows all five public sections.minimalkeeps status, amount, currency, timestamps, execution history, and Proof. Other fields usehidden_by_ownermarkers.offreturns the same 404 response as an unknown receipt.
Without an owner override, demo and sandbox tenants default to full. Production tenants default to minimal.
An authenticated Console user who is an active tenant admin can update the setting through the business-profile facade:
Use full, minimal, or off. Send null to clear the override and restore the tenant-kind default.
Browser Access, Caching, and Errors
The two public receipt endpoints allow cross-origin reads from every origin. They return Access-Control-Allow-Origin: *, do not allow credentials, vary on Origin, and accept GET, HEAD, and OPTIONS. An OPTIONS preflight returns 204. This public CORS posture does not change other API routes.
Successful JSON and HTML responses return:
The limit is 60 requests per minute for each Fastify rate-limit key. Rate-limit responses return HTTP 429.
Unknown ids, malformed ids, hidden receipts, ambiguous ids, and inaccessible receipts all return the same HTTP 404 envelope. The response does not reveal whether a record exists or why it is unavailable. Receipt 404 and 429 responses carry the same public CORS headers.
Last updated
