How Peon works
Connect AI to multiple
client accounts.
Create each client and assign their app accounts once. Connect the AI tool you already use, then ask for work by naming the client instead of switching accounts or pasting connection details.
Set up once
Four steps before
the first routed request.
The client-account graph is reusable. You do not rebuild it in every AI conversation or separately for every compatible agent.
- AC01
Create the client
Add the person or company your AI should recognize.
02Assign their accounts
Attach the email, files, analytics, and workspaces that belong to them.
- Read-only03
Choose their access
Set full, read-only, or curated access and declare the client data boundary.
04Connect your AI
Authorize the AI tool you use once. After that, begin with the client's name.
Every request
Name the client.
Follow one deterministic path.
The request stays short. Peon does the client resolution, selected-account lookup, access check, provider dispatch, and response disclosure behind it.
- 01
Resolve the client
Peon matches the name, company, alias, or exact client ID. Ambiguous matches are never guessed. - 02
Load assigned accounts
Only the app accounts attached to that client are available for the request. - 03
Apply access and data boundaries
Peon checks the allowed tools and narrows client data before the provider action runs where supported. - 04
Return the result and trail
The AI receives the provider result with client context, boundary disclosure, counts, pagination, and an execution receipt.
“For Acme, summarize this week's client work from email, Notion, Analytics, and the project workspace.”
The prompt names the client and the outcome. It does not contain provider keys, raw connection IDs, or an account-selection procedure.
When Peon pauses
Clear stops are better
than confident mistakes.
A safe refusal is part of the product. Peon makes account ambiguity and access boundaries visible instead of burying them in provider errors.
- 01
The client name is ambiguous
Peon returns the possible clients and asks for an explicit choice. - 02
The client has no account for that app
The request names the missing assignment instead of selecting another account. - 03
The action is outside the access mode
Peon refuses it before provider execution and reports that the scope is intentional. - 04
One app cannot return an update
A multi-app collection can still return the useful results and identify what was skipped or failed.
Connect the AI you use
One client setup.
Several ways to work.
Each installation has its own revocable identity. Once a compatible agent loads Peon's five tools, the same client-account graph is ready to use.
Start free
Set up each client once. Work by name from then on.
Create your account, add one client, and connect the app accounts that belong to them. No card required.