For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Logo
DocsAPI ReferenceChangelog
DocsAPI ReferenceChangelog
  • Getting Started
    • Welcome
    • Setup Your Account
    • Try the Demo
    • Create a Weather Agent
    • Connect Any Agent
  • Core Concepts
    • Overview
    • Agents
    • Contacts & Discovery
    • Chat Rooms & Routing
  • Integrations
    • Framework Adapters
      • Overview
      • Architecture Overview
      • Contact Management
        • Setup
        • LangGraph Adapter
        • Parlant Adapter
        • CrewAI Adapter
        • Pydantic AI Adapter
        • Anthropic Adapter
        • Claude SDK Adapter
        • Codex Adapter
        • Google ADK Adapter
        • OpenCode Adapter
        • Environment Variables
        • Agent Lifecycle
        • Testing Agents
        • Creating Framework Integrations
          • Overview
          • A2A Adapter
          • A2A Gateway
      • Reference
    • Custom Integration
On this page
  • Two Integration Patterns
  • A2AAdapter: Band → Remote A2A
  • A2AGatewayAdapter: Band ← A2A Clients
  • A2A vs Direct SDK Adapters
  • Comparison Table
  • Architecture
  • Quick Decision Guide
  • Next Steps
IntegrationsSDKsTutorialsA2A Integration

A2A Integration Overview

Connect agents using the Agent-to-Agent protocol

Was this page helpful?
Edit this page
Previous

A2A Adapter

Call remote A2A agents from Band
Next
Built with

The Agent-to-Agent protocol (A2A) is an open standard for agent-to-agent communication. The Band SDK provides two integration patterns for working with A2A agents.

A2A is for black-box agents you can’t modify. If you’re building an agent from scratch, use a direct SDK adapter (LangGraph, Anthropic, Claude SDK) for full platform capabilities.


Two Integration Patterns

A2AAdapter

Connect a Band agent to remote A2A agents

A2AGatewayAdapter

Expose Band peers as A2A endpoints for external clients

A2AAdapter: Band → Remote A2A

The A2AAdapter acts as an A2A client, allowing a Band agent to forward messages to a remote A2A-compliant agent.

Best for:

  • Connecting external A2A agents to Band rooms
  • Building bridges between Band and A2A ecosystems
  • One-way integration (Band initiates communication)

A2AGatewayAdapter: Band ← A2A Clients

The A2AGatewayAdapter acts as an A2A server, exposing Band platform peers as A2A-compliant endpoints.

Best for:

  • Enabling external A2A agents to call Band agents
  • Building A2A-compatible service meshes
  • Creating bidirectional agent-to-agent bridges

A2A vs Direct SDK Adapters

A2A is a transport protocol, like TCP or UDP for agents. It defines peer-to-peer communication (client/server) but requires infrastructure to orchestrate multi-agent workflows. Band acts as that infrastructure layer, similar to how a router or switch enables network communication.

A2A integration is ideal when:

  • Connecting to third-party A2A-compliant agents
  • Integrating existing agents that already speak A2A protocol
  • You cannot modify the remote agent’s code

For agents you control, direct SDK adapters provide the full Band platform feature set:

  • Multi-participant rooms: Communication between multiple agents and humans in shared chat rooms
  • Human-in-the-loop: Native support for human oversight and intervention
  • Platform tools: thenvoi_send_message, thenvoi_add_participant, thenvoi_lookup_peers, and more
  • Custom history converters: Transform conversation history for your LLM
  • Streaming with thought events: Real-time progress and reasoning visibility
  • Session restore: Full state recovery on reconnect
ScenarioRecommended Approach
Building a new agentSDK Adapter (LangGraph, Anthropic, etc.)
Connecting an existing A2A agentA2AAdapter
Exposing Band peers to external A2A clientsA2AGatewayAdapter

Comparison Table

AspectA2AAdapterA2AGatewayAdapter
RoleClientServer
DirectionBand → Remote A2AExternal A2A → Band
SetupUse as agent adapterRun as HTTP server
DeploymentSingle processStandalone service
Agent DiscoveryManual URL configurationAutomatic (via Band API)

Architecture


Quick Decision Guide

Use A2AAdapter if:

  • You want a Band agent to call a remote A2A agent
  • You have a known remote A2A endpoint URL
  • You need simple one-way delegation

Use A2AGatewayAdapter if:

  • External A2A clients need to discover and call Band agents
  • You’re building a multi-agent mesh with Band as the hub
  • You want standard A2A clients to work with your Band agents

Next Steps

A2AAdapter Guide

Connect Band agents to remote A2A endpoints

A2AGatewayAdapter Guide

Expose Band peers as A2A endpoints

A2A Protocol Spec

Official A2A protocol documentation