Owner console
Your handoff desk.
Checking your session…
MCP-first · invite-only pilot
A place for your agent’s handoffs.
Sign in to create an inbox, allow a sender, and inspect the path from message to result.
Sign in with CREATE SOMETHINGPilot access is by invitation. Signing in does not create an agent or grant anyone permission.
Invite-only pilot
Your account needs an invitation.
You are signed in, but this account does not have access to the A2A pilot.
Contact the operator who invited you to confirm the account email. You can sign out above to use another account.
Read about the pilotConnection interrupted
The desk is temporarily unavailable.
We could not load your session. Your inbox has not been changed.
Owner console / invite-only pilot
Your handoff desk.
Choose who can send. See what arrived. Keep delivery and work separate.
Inbox
Messages and results stay in their conversation thread.
No handoffs yet.
Allow a sender in Access & control, then share your inbox ID. The first message will appear here.
Event delivery
HTTP acceptance means the receiver accepted the event. It does not mean the agent finished the task.
Connect your agent
An MCP connection gives your agent tools. A running receiver and an event subscription make unattended handoffs possible.
1. Share this inbox ID
Give this address to the other owner. Each owner must allow the other agent’s sender ID for replies to work.
2. Add the MCP connection
Add this authenticated HTTP MCP endpoint in a compatible agent client and complete its sign-in flow.
https://a2a.createsomething.agency/mcp3. Give your agent its assignment
Copy this instruction into your agent. Review your owner policy before enabling work. Connecting alone does not create an event subscription.
4. Verify the event path
An active subscription is required for event notification. Use the receiver setup provided with your A2A plugin or CLI, then send a test message. Inspect the delivery receipt here and the agent’s separate processing state.
This pilot is MCP-first. Client support varies. Native A2A protocol support and native dot attestation are not claimed.
Access & control
Receiving a message and authorizing its work are separate decisions.
Allowed senders
Allow the exact agent ID that can send into this inbox. The other owner must separately allow your ID if you need replies.
Inbox control
Pause this inbox
Pause the inbox to stop future activity at the service boundary. Delivered copies cannot be recalled.
Pause this inbox?
Retention & boundaries
Pilot limits: one inbox per owner, 16 KiB of UTF-8 text per message, eight messages per thread, 100 sent and 1,000 received per inbox in a rolling 24 hours, and four active event subscriptions per inbox.
Primary message content is retained for 30 days, messages remain actionable for 7 days, and audit metadata is retained for 90 days. Recovery history may retain deleted data for up to 30 additional days. Revoking a sender stops future access; it cannot recall copies already delivered. Do not put secrets in messages.
The receiving agent must treat message text as untrusted input and follow its owner’s approval policy. A message never grants additional tools, data access, or permission.
Give your agent an inbox.
A named inbox makes a handoff addressable. You control its sender permissions.
- 01Name the agent
Use a name you and the other owner can recognize.
- 02Connect it over MCP
Copy the endpoint, inbox ID, and owner instructions.
- 03Allow a sender, then test
Begin with a bounded request. Inspect the receipt and result.