Approval decisions
LiveEvery action that writes outside your workspace passes through the approvals queue. What was proposed, who approved or rejected it, and when, is recorded.
AI usage proof is a verifiable record of what an AI did for your business: which actions ran, who approved them, and what changed. Riley records it honestly, so you can show what your AI actually did.
Start freeAI usage proof is a verifiable record of what an AI did for your business: which actions ran, who approved them, and what changed. It turns a vague claim like "the AI handled it" into evidence a client or a manager can check.
Riley is the AI coworker that proves its work. It records approval decisions, signs receipts of completed work, and keeps a per-key access record, so the answer to "what did your AI do?" is a document, not a memory.
If AI touches work that other people rely on, sooner or later you have to show what it did.
Show each client what the AI did on their account, and that a person on your team approved the decisions that mattered.
Keep a clear record of what got answered, fixed, and posted, so you always know what happened while you were busy.
Give a manager a usage picture of AI-assisted work without asking anyone to reconstruct it from memory.
Hand over a verifiable record at the end of an engagement instead of a summary the client has to take on trust.
When AI does work on a real account, the value is easy to lose. The action runs, the moment passes, and by the time someone asks what happened, the only record is what a person remembers. That is fine until a client questions the bill, a manager asks for an audit, or a mistake needs tracing.
The honest version is harder than it sounds. It is not enough to log that "something ran." Real usage proof has to show what was proposed, who approved it, what actually changed, and how you know. Anything less is a claim dressed up as a record.
You do not assemble usage proof by hand. Riley records it as a byproduct of the same loop it runs to do the work.
Honest statuses only. Here is what is live today and what is still rolling out.
Every action that writes outside your workspace passes through the approvals queue. What was proposed, who approved or rejected it, and when, is recorded.
Completed work is assembled into signed receipts with a public verify link. That is a record you can hand to a client and they can check it themselves.
Each AI surface connects with its own per-workspace key. See which keys exist, when each was last used, and revoke any of them from Settings.
A per-surface breakdown of which AI client asked for what, over time, in one view. This is rolling out and is labeled coming soon everywhere until it ships.
Put together, Riley's records answer the three questions any usage audit asks. Approval history answers who signed off. Signed receipts answer what actually happened. Per-key access answers which surface did it and when. Each one is recorded as the work happens, and each carries an honest note about anything that could not be confirmed.
Riley records three things right now: approval decisions, meaning what was proposed and who approved or rejected it; signed receipts of completed work with a public verify link; and per-key access, so you can see which AI surface connected and when each key was last used. A per-surface usage log is rolling out and is labeled coming soon until it ships.
When you run AI on behalf of clients, someone eventually asks what it did and whether a person stood behind the decisions that mattered. Approval history answers who signed off, signed receipts answer what actually happened, and per-key access answers which surface did it and when. That is the difference between saying AI helped and proving what it did.
They are related. A proof receipt is a signed weekly record of the work Riley completed. AI usage proof is the wider picture: the receipts plus approval decisions and per-key access records. Together they let you show both what was done and that it was done under your control.
Yes. Every signed receipt carries a public verify link that anyone can open to confirm it is real, without an account or a login. You choose what to share and with whom.
Put your work on one loop and let the proof record itself. Start free, no card to begin.