A2A protocol

Rightbrain supports the open Agent2Agent (A2A) protocol for interoperability between AI agents. A2A lets an agent built on one framework call an agent built on another, without a custom integration on either side. When you expose a Rightbrain task over A2A, other agent frameworks can invoke it as if it were one of their own agents.

A2A vs MCP

Rightbrain speaks two interop protocols. They target different callers:

If you are wiring a task into a coding assistant or chat client, use MCP. If you are building a multi-agent system where agents hand work to each other, use A2A.

Expose a task over A2A

A task is exposed to A2A when its exposed_to_agents flag is set. Once enabled, it appears in the project’s A2A registry.

POST https://app.rightbrain.ai/api/v1/{project_id}/a2a/agents/{agent_id}

Two discovery endpoints let A2A clients find your agents: GET .../a2a/agents lists every task in the project exposed to agents, and GET .../a2a/agents/{agent_id}/.well-known/agent-card returns the standard A2A agent card for one of them.

External agent frameworks that support A2A can then discover the task’s capabilities and send it requests over JSON-RPC. The task runs on Rightbrain with its configured model, prompt, and output schema, and returns a structured result to the calling agent.

The JSON-RPC endpoint currently supports message/send. Other methods return JSON-RPC method-not-found error -32601.

The discovery and JSON-RPC endpoints require a bearer credential. Send an API key or OAuth access token for a user with access to the project.

Next steps