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.
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.
Export a POV deck (PDF)
The same page can open the print-ready POV deck for an account in a new tab — data-driven charts included — so you can File → Print → Save as PDF. Generate the deck first, then enter the account id to open it.
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.