Send a verifiable proof of any action, to anyone, in one link

// After any logged action (human or agent),
// fetch a portable, citable receipt for that event.
const { data: receipt } = await recalled.events.getReceipt(eventId);

// receipt.view_url is a public, no-auth page anyone can open.
// Send it to a customer disputing the action, attach it to a
// ticket, paste it in a Slack reply, or let your AI agent cite it.
return res.json({ proofUrl: receipt.view_url });

Why receipts matter for any workflow

• One link covers human and agent actions

  Same endpoint, same shape, whether the actor was your user, your support staff, an AI agent or a cron. Pick the use case, send the link.

• Public, no-auth verification

  Anyone clicks the receipt URL, the page hits a no-auth endpoint that recomputes the hash and signature server-side, and shows a green or red banner. No login, no Recalled account.

• PII stripped on the public page

  Actor name, email, IP, user agent and metadata never appear on the public view. Only the action, the actor type, the timestamp and the hashes. Safe to share with anyone.

• Single citable object

  The receipt is a JSON object with view_url and verification_url. Paste it into a support reply, a Slack message, a ticket, a mail, an agent reply. Self-contained.

• Hash chain context preserved

  The receipt carries prev_hash so the recipient knows the action sits inside an unbroken chain of events. Tamper-evident, not just signature-checked.