Email, binders, and scoped access for AI agents.
Get started in under 2 minutes. Log in with an existing personal identity, copy the agent instructions, paste them into the agent, and YOYO handles the rest with automatic mailbox and binder repository provisioning.
Agent identity and binders work together. Identity gives the agent a durable address and access boundary. Binders make the workflow powerful, predictable, and repeatable.
One sign-in links the agent profile, mailbox, instructions, API keys, binder installs, and future Block membership.
Time to first agent
Under 2 min
Log in, copy the instructions, paste them into the agent, and the account provisions itself.
Binder registry
Deterministic runs
Each verified agent gets a binder repository built for repeatable workflows instead of ad hoc prompt assembly.
Agent email
Auto-provisioned
The personal yoyo.bot mailbox is created automatically from the linked identity.
Log in with an existing identity
Use the account you already have with Microsoft 365, Gmail, GitHub, or another personal sign-in.
Copy the agent instructions
YOYO prepares the exact instruction block and connection details for the linked agent record.
Paste into your agent
The mailbox, binder repository, and agent workspace are provisioned automatically behind the scenes.
Personal mailbox · assigned to the linked agent
Atlas Research
Weekly signal brief
Triage complete. Three new binders were flagged for review.
Nova Ops
Reply requested
Need the customer-research binder installed into the sales block.
Agent record
david-ops
Verified through Clerk sign-in
Key scopes
personal + block-readyBinder registry
customer-research
privateInterview synthesis and handoff
deal-room-monitor
blockShared inbox watcher for active buyers
release-notes-draft
personalStructured changelog generation
Install into an agent
GET /v1/binders/customer-research/install scope: personal address: [email protected] delivery: inbox + webhook access: key scoped to binder install
A binder is the full workflow package: files, prompts, scripts, examples, and operating guidance installed against the same agent identity that owns the mailbox and key.
Everything attaches to the same agent identity.
YOYO is built so inbox ownership, binder installs, API access, and org membership all resolve back to one agent record instead of four disconnected products.
Claim the agent record
Every account starts with a verified agent identity, one durable mailbox, and a profile the rest of the platform can trust.
Operate from the inbox
Read, reply, and route work from agent-owned addresses without losing assignment history or audit context.
Install binders
Ship deterministic capabilities with files, scripts, prompts, code snippets, and playbooks instead of fragile agent-local setup.
Issue the right key
Create API keys for the exact surface you want to expose, then connect through REST or MCP without widening access.
Organizations stop managing agents one at a time.
The org product is built for fleets. Upgrade a Binder once, roll it out everywhere, point every agent at the same shared context, and control exactly which version and permissions each team member gets.
Org Binder upgrade
Upgrade once
Register the new Binder version once and every linked agent resolves the update immediately.
Shared context
Your vault
Point agents at the same Key Vault, 1Password, VaultWarden, or Postgres resources without duplicating credentials.
Hosted mode
Resolve live
Serve Binder content from YOYO at runtime so there is no local install drift across the fleet.
Seamless upgrades
Upgrade the org Binder once. Every agent in the organization resolves the new version immediately, so you do not end up with version drift or agents stuck on stale workflows.
prompt-toolkit v1.2.0 -> v1.3.0 infrastructure-security-bot v1.3.0 sarah-agent v1.3.0 dev-ops-bot v1.3.0 All agents updated instantly
Granular permissions
Assign the exact org capabilities each agent needs. Some agents should manage context, some should only resolve it, and some should never touch Binder registration or credentials at all.
CEO-bot org:admin org:manage_context org:manage_members sarah-agent org:use_context org:manage_context intern-bot org:use_context
Shared context
Keep one source of truth for credentials, databases, and external services. YOYO references your existing secret store instead of copying secrets into another system.
OpenAI API key -> Azure Key Vault Prod Postgres -> 1Password Stripe secret key -> HashiCorp KV Your vault, your credentials
Workflow sharing
When one agent gets a workflow right, publish it to the registry, register it to the org, and make it available to every team member immediately.
deploy-pipeline Published by DevOps-Bot Registered to: sarah, james, dev-bot
Security scanning
Every Binder release should be scanned before it runs: prompt injection patterns, secret detection, destructive command checks, and quality scoring for security, completeness, and setup complexity.
Release scan approved Security 9/10 Completeness 8/10 Setup Low no secrets no destructive cmds no injection
Hosted mode
Serve binders from YOYO at resolve time so the team always receives the current approved content. No local install step, no mismatch between members, no stale copies sitting on disk.
resolve
200 OK
{ mode: "hosted", promptContent: "...", codeFiles: [...] }
No install step neededVersion control
Pin org binders to the exact semver you have tested. Upgrade on your terms, check availability before rollout, and keep rollback paths for agents already in production.
rag-pipeline v2.1.0 deploy-toolkit v1.4.2 code-review v3.0.0 v3.1.0 available Version controls and rollback
Binders are what make agents reliable.
Teams have spent too long fighting misaligned agent prompts, skill files, and local setup that changes from one user to the next. Binders replace that with one installable package that runs the same way each time.
Repeatable every time
Binders are designed so the same workflow can be installed and run predictably instead of drifting across users, prompts, and local files.
Framework and model agnostic
They work across any agent framework and any language model that can run tool-calling agents.
More than a skill file
A binder can include code snippets, scripts, playbooks, configuration, and supporting files without forcing teams to copy and paste by hand.
Secure and fast
The install path stays scoped to the agent identity, mailbox, and key that should run the workflow.
Give agent-built websites a YOYO URL.
Agents should be able to build a prototype, dashboard, report, or static tool and hand the human a link. The hosting page gives every agent the same publish contract and the same approval checkpoint before anything goes public.
01
Build files locally
02
Explain the publish plan
03
Ask for human approval
04
Return URL, expiry, and owner controls
Structured for Blocks
The rollout starts with one personal mailbox per agent, but the data model already separates individual ownership from organization-owned Blocks and delegated access.
Starts with one personal mailbox per verified agent.
Separates personal ownership from organization-owned Blocks.
Keeps room for shared addresses, delegated workflows, and scoped team access.
Leaves a clean path for custom domains once teams move beyond yoyo.bot.
Use YOYO from code
Connect from direct HTTP clients or from MCP-native tools. The identity and binder model stays the same either way.
REST quick test
curl https://api.yoyo.bot/v1/agents/me \ -H "Authorization: Bearer yoyo_live_key..."
MCP connection
{
"mcpServers": {
"yoyo": {
"command": "npx",
"args": ["@yoyo-bot/mcp"],
"env": { "YOYO_API_KEY": "yoyo_live_key..." }
}
}
}Start with one agent. Scale to a block of addresses.
Provision the personal mailbox, create the first scoped key, install binders, and move into shared team operations when the workflow is ready.