Use cases · AI automation agencies
audit the outcome · verify activation · prove it every Friday
Teams building AI systems for clients. Riley is the accountable layer underneath: one gated door for AI actions, watches on the automations, and proof of what the stack did.
What Riley is usually hired for in this setup. Statuses are honest: live means it works today, and coming soon means it does not exist yet.
Requests that arrive through any connected AI surface pass through the same gate: external writes wait in your approvals queue, whoever asked for them.
Connect Riley to Claude, Cursor, ChatGPT where supported, and other MCP clients with a per-workspace key. Same worker, same rules, wherever you ask.
Register your own MCP server or import an OpenAPI spec, and Riley uses those tools under the same approval and receipt rules as everything else.
Riley will watch the automations and scheduled jobs you rely on and raise a finding when one stops running or starts failing.
Riley will assemble AI activity across surfaces into a usage receipt: what was asked, what shipped, and who approved it. Built for teams that answer for their AI use.
Riley assembles everything it completed into a signed weekly receipt with a public verification link, so the people you answer to can check the work themselves.
Trigger: Will record continuously as AI surfaces use Riley.
Approval: Logging is read only; sharing the usage receipt is your call.
Trigger: Will run on a schedule against automations you register.
Approval: Watching is read only; repairs wait for approval.
Trigger: Riley detects a problem on anything it watches.
Approval: Every fix card waits for your approval before anything changes.
Trigger: Whatever you and the Riley team define for it.
Approval: Approval rules are set when the workflow is built; external writes always queue.
Trigger: Runs every week on your schedule.
Approval: Built from already-approved work; sending it to a client is your call.
The connections this setup usually starts with. You grant access, and you can revoke any connection at any time.
The surfaces this setup usually works from. The same rules apply on every one of them.
Connect your tools, approve the first drafts, and get a signed receipt of the work every week.