Photo: Tima Miroshnichenko / Pexels
The new adapter lets Fetch.ai's autonomous agents communicate with external AI agents through Google-linked A2A protocol
Fetch.ai has shipped a tool that could quietly reshape how autonomous AI agents talk to each other across platforms. The A2A Outbound Adapter, part of the project’s uAgents-adapter package, gives developers a straightforward way to connect Fetch.ai’s native agents with any external agent that speaks the A2A (Agent-to-Agent) Protocol.
The A2A Protocol is an interoperability standard notably linked to Google Cloud systems. It defines how independent AI agents find each other, exchange messages, and coordinate tasks. Fetch.ai’s new adapter bridges the gap between its own agent ecosystem, which includes both uAgents and Agentverse agents, and the broader universe of A2A-compatible systems.
Two configuration modes are available. The SingleA2AAdapter handles connections to one external A2A server, while the MultiA2AAdapter supports simultaneous connections to multiple servers with multi-port operation. Under the hood, the adapter includes chat protocol forwarding, automatic agent discovery and registration, health monitoring, and routing strategies like keyword matching.
The adapter requires Python 3.10 or higher and is available in versions 0.6.0 and 0.6.2 of the uAgents-adapter package. Documentation lives on both innovationlab.fetch.ai and uagents.fetch.ai.
Payment bridging and real-world use cases #
The adapter includes a payment bridging mechanism that translates between A2A and AP2 payment mandates and Fetch.ai’s own Payment Protocol. Fetch.ai has already demonstrated an A2A cart store example that utilizes Skyfire payments, showing end-to-end transactions flowing through the adapter in a decentralized environment.
Positioning for A2A Protocol v1.0.0 #
Version 1.0.0 of the A2A Protocol is anticipated for March 2026 and will include breaking changes along with multi-tenancy support. Initial features of the A2A adapter were incorporated into Fetch.ai’s uAgents repository in early March 2026. No press release or specific launch date for the Outbound Adapter was identified, suggesting it is an incremental addition developed across 2025-2026.
The FET token merged into the Artificial Superintelligence Alliance (ASI) alongside SingularityNET and Ocean Protocol. No new token mechanisms or staking incentives are tied to the adapter itself.
Disclosure: This article was edited by Editorial Team. For more information on how we create and review content, see our