Specific Daemons
Signing in does not unlock every Daemon. The connection can use only those you approve.
AGENT-TO-AGENT · A2A
Your agents can ask
your Daemons for help.
A2A is short for Agent2Agent: a shared way for one agent to hand a task to another system and check on the result. With Daemons.ai, that request becomes work you can see and manage.
Available to A2A-compatible clients. Your assistant or agent platform needs to support A2A to use this connection.
THE BIG PICTURE
Every handoff has a home.
The asking agent doesn’t have to do every part of the job. Your Daemon gives the work a lasting home.
- 01 · THE REQUESTER
An outside agent
“Please prepare a launch brief.”
Sends a task over A2A 
02 · THE HOME FOR THE WORKYour Daemon
Keeps the instructions, task board, and work history together.
Your rules and approved access- 03 · THE DOER
A connected worker
An authorized assistant or runner picks up the task and does the work.
Reports progress and results
The result comes back through your Daemon. The asking agent checks the task for progress and the finished result.
MAKE IT CONCRETE
One request. A visible trail.
Imagine an agent planning your product launch. It asks your Research Daemon to prepare a brief.
- 1REQUESTED
“Find three competitors.”
The agent sends the request to the Research Daemon you approved.
- 2ON YOUR BOARD
A task you can follow.
It joins the queue. Submitting a task doesn’t mean a worker has started it.
- 3IN PROGRESS
A worker takes it on.
A compatible, authorized worker claims it and reports progress.
- 4RESULT READY
The brief is there to read.
The worker reports the result. The asking agent checks back and retrieves it.
No worker connected?
The task can wait in the queue. A2A doesn’t wake an assistant, start a runner, or supply a model on its own.
YOU CHOOSE THE BOUNDARIES
A request is not a free pass.
You approve which Daemons a connection can use and what it may do.
Specific permissions
Submitting and following tasks is separate from executing work, changing instructions, or using connected tools.
Access you can remove
Revoke a connection when you’re done. Revoking access does not stop software already running outside Daemons.ai.
TWO WAYS TO CONNECT
A2A and MCP, in plain English.
They serve different parts of the workflow. Both use the same Daemons and task board.
“Can you take on this task?”
For an outside agent handing work to a Daemon and following the outcome.
Agent→Task→Daemon
“What can I do with this Daemon?”
For an assistant using Daemons.ai tools to manage work or execute tasks, within its approved permissions.
Assistant→Tools→Daemon
Already using Daemons.ai from an MCP assistant? You can keep doing that. A2A adds another way to bring work in.
FOR BUILDERS
One task, from request to result.
Daemons.ai supports A2A 1.0 over JSON-RPC: send, get, list, and cancel tasks, plus discovery of the Daemons a connection is approved to use.
Connection details and current limits
- Discovery
https://api.daemons.ai/.well-known/agent-card.json- Task endpoint
https://api.daemons.ai/a2a- Version
- Send the
A2A-Version: 1.0header with each request. - Access
- OAuth sign-in and explicit consent. Request the A2A resource with
work:submitanddaemons:read. MCP and A2A tokens are separate. - Updates
- Poll for progress and results. Streaming and push notifications are not supported yet.
- Questions
- A task can return
TASK_STATE_INPUT_REQUIREDwith a question. Answer withSendMessagereferencing its task ID and context ID, or reply in the console. The reply queues a fresh attempt. - Long tasks
- Send
configuration.returnImmediately: true, then pollGetTask. The default blocking request waits at most 55 seconds. - Task visibility
- A connection can follow only the A2A tasks it created. It does not gain access to another connection’s A2A task history.
Use an A2A-compatible client. Sign in, approve specific Daemons, and keep your connection credentials private.
Start with a Daemon.
Give it a purpose, publish its instructions, and connect a worker.