Agent activity & receipts
Every agent action, explained: what was done, the data it used, the citations that justified it, and whether it succeeded, as a per-account chain of touches.
Overview
When an agent updates a CRM, drafts outreach, or enriches a record on your behalf, it leaves a receipt. A receipt binds four things: the action, the data used, the why (the playbook citations it was grounded in), and the outcome. /receipts shows that chain, newest first.
Scoped to your account. Payloads are redacted before display: secret-like keys are masked and nested records are reduced to their shape, so no raw customer data is exposed in this view.
What it shows
- Each touch. Timestamp, the provider + action (e.g.
salesforce · opp.update_stage), an applied / failed outcome badge, and the origin (a brain recommendation, a manual action, or a cron). - Data used. The (redacted) fields the action acted on.
- Why. The brain citations the action referenced.
- Per-account filter. Enter an account domain (e.g.
acme.com) to see just that account's history of agent touches over time.
POV deck (PDF)
The same page builds and opens a five-slide "why we're a fit" deck for one account, with data-driven charts, ready to File → Print → Save as PDF.
Enter the account id and the card tells you whether that account already has a deck. Generate deck builds a fresh one from the account's own data and opens it; Open deck opens the last one you built without spending another AI call. Generating runs an AI pass and is capped at five decks every ten minutes.
If it cannot build one, the card says which reason applies rather than failing silently: no account with that id, no active plan, the rate limit, or the deployment having no AI key. Until 2026-08-22 the card could only open a deck and nothing in the product could generate one, so it answered "No deck yet, generate one first" for everybody.
When a load fails
If the receipt history cannot be read, the page says so. It does not fall back to the empty state: "no agent touches recorded yet" is a claim about your account, and a failed request is not evidence for it. Refresh to retry.
Where the data comes from
Receipts are a thin layer over the writeback log every agent action already records; the page reads GET /api/me/receipts. Nothing new is tracked; the receipt just makes the existing action trail queryable and readable.