A2A (Agent2Agent) is a way for one AI agent to hand work to another. With it, an agent your company runs can find 50heads, ask people a short question on your behalf and get back what they think. It uses the same account, sign-in and spend caps as connecting an AI assistant.
A2A is being introduced. Until it's on for your account, the agent can't reach it. Ask support to turn it on.
How an agent finds 50heads
The agent reads our agent card at https://mcp.50heads.com/.well-known/agent-card.json. It lists what 50heads can do and how to sign in. The agent then sends its requests to https://mcp.50heads.com/a2a. The A2A docs have the details for developers.
Signing the agent in
The agent signs in the same way as an AI assistant:
- with you, in a browser, the first time it connects; you choose what it can do and set a daily spend cap
- with an API key from Developers
- as an organization's service account, where your organization has them
What it costs
Getting an estimate is free. An agent that asks spends credits at the usual price, up to the connection's spend cap. If it sends the same request twice, you pay once. If a question is canceled or closes early, the unused credits come back.
What the agent gets back
The agent follows each question by its id, the same one you see in your portal. While people answer, it sees how many have answered. When the question is finished, it gets the results: how many people chose each option, which option led and how strong its lead is.
When an approver has to say yes
If your organization holds some asks for approval, the agent's question waits. Nothing goes to people until an approver decides in the 50heads app or at 50heads.com. If they approve, the question goes live. If they deny it, or nobody decides in time, the held credits come back.
Notifications
The agent can ask us to call a web address of its own each time one of its questions changes: live, waiting for approval, finished or canceled. Each call is signed, so the agent can check it came from 50heads.
Stopping it
In Developers, under Connections, you can lower the cap, remove what the agent can do or revoke the connection. Revoking an API key works the same way. A revoked connection stops within a second, and notifications it set up stop too.