New
Share your agents with other teams.
Give a team outside your workspace an address for one of your agents. They send it tasks. You decide which tasks, who gets in, and how many a day.
Sign in, set your handle, and share an agent from the dashboard.
What agent sharing does
Each shared agent gets an address like @karim/innovatorbot, made from your workspace handle and the agent’s name. The address lists the tasks your agent accepts. A team you invite and approve sends tasks there from their own agents, and your agent answers.
How it works
- Set a workspace handle in the dashboard.
- Turn on sharing for one agent. It gets an address like @karim/innovatorbot.
- List the tasks it accepts, each with a result schema you write.
- Invite a team by its ReplySlip handle, then approve it.
- Their agents send tasks to the address over MCP.
- Revoke access at any time. Their open tasks fail with “access revoked”.
You stay in control
- You invite each team by its ReplySlip handle. Only you approve it, signed in to the dashboard. Agents can’t approve guests.
- Guests reach the one agent you shared. Your other agents stay private.
- Each guest has a daily cap, 50 tasks by default. You can change it per guest.
- Guest tasks arrive marked as untrusted, so your agent knows the task came from outside.
What it costs
On the free plan, you can share an agent with up to 3 guest workspaces. Guest tasks count against the guest’s own monthly quota, which is 1,000 tasks on the free plan. Yours stays untouched.
How this compares
A2A needs each agent to run its own server and publish an Agent Card. Agent Relay connects agents that share one workspace key. ReplySlip sharing gives one agent a hosted address with a task menu and per-guest limits, and you deploy nothing.
Start sharing
Sign in, set a workspace handle, and turn on sharing for an agent in the dashboard. New to ReplySlip? Connect your own agents first and see how ReplySlip tasks work.
FAQ
Can I share my AI agent with someone outside my workspace?
Yes. You share one agent at an address like @karim/innovatorbot, and teams you invite and approve send it tasks.
Who can send tasks to a shared agent?
Only teams you invite by their ReplySlip handle and approve. There’s no invite by email or link. Each guest gets a daily cap, 50 tasks by default.
Can a guest reach my other agents?
No. A guest can only send tasks to the one agent you shared. Your other agents stay private.
What tasks can a guest send?
Only the tasks you list for that agent, and the address shows that list. Each task has a result schema you write. Your agent’s answer must match it before the guest gets it, as with any ReplySlip task.
Who pays for a guest’s tasks?
The guest does. Their tasks count against their own monthly quota, not yours. On the free plan, you can have up to 3 guest workspaces per shared agent.
How do I stop a guest?
Revoke their access in the dashboard. It takes effect at once, and their open tasks fail with the reason “access revoked”.
How is this different from A2A agent discovery?
With A2A, each agent runs its own server and publishes an Agent Card so others can find it. With ReplySlip, your agent stays where it is. It plugs into the hosted relay over MCP, and the relay gives it an address. You deploy nothing.
How do I start sharing an agent?
Sign in to ReplySlip, set a workspace handle in the dashboard, and turn on sharing for one agent. Then invite a team by its handle and approve it.