OpenAgents 整合 A2A 協議,實現 LangGraph、CrewAI 和 Pydantic AI 代理的無縫互操作性

OpenAgents 整合 A2A 協議,實現 LangGraph、CrewAI 和 Pydantic AI 代理的無縫互操作性

Hacker News·

OpenAgents 現已支援 Agent2Agent (A2A) 協議,這是一種標準化的 AI 代理通訊方式。此整合使使用 LangGraph、CrewAI 和 Pydantic AI 等框架建構的代理能夠在 OpenAgents 網絡內無縫連接和協作,解決了 AI 代理生態系統碎片化的挑戰。

Image

A2A Protocol: Connect Any AI Agent to OpenAgents

We're thrilled to announce that OpenAgents now supports the Agent2Agent (A2A) protocol! This means you can seamlessly connect AI agents built with LangGraph, CrewAI, Pydantic AI, or any A2A-compatible framework to your OpenAgents network.

The Challenge: Agent Interoperability

The AI agent ecosystem is fragmented. You might have:

Getting these agents to work together has been... challenging.

"How do I make my LangGraph agent talk to my OpenAgents network?"

"I want to use this amazing A2A agent I found, but it's not built with our framework."

"Why can't agents just discover each other and collaborate?"

The Solution: A2A Protocol Integration

A2A (Agent2Agent) is an open protocol originally developed by Google and now managed by the Linux Foundation. It's the "HTTP for AI agents" - a common language that lets any agent talk to any other agent.

And now, OpenAgents speaks A2A fluently.

One Port, All Protocols

A2A joins MCP and Studio on the unified HTTP transport:

Everything runs on port 8700:

How It Works

1. Discover Agents via Agent Cards

Every A2A agent publishes an Agent Card describing its capabilities:

2. Send Messages with JSON-RPC

A2A uses JSON-RPC 2.0 - simple, standard, and easy to implement:

3. Connect Remote A2A Agents

External A2A agents can join your network:

The network automatically:

Cross-Protocol Magic

Here's where it gets exciting. Your OpenAgents network now has a unified registry:

An event from your gRPC translator agent can be sent to a remote LangGraph agent - the network handles the protocol translation automatically.

Real-World Example: Building a Research Team

Imagine building a research team with agents from different frameworks:

A2A vs MCP: Better Together

They're complementary! An agent might use MCP to access tools and A2A to collaborate with other agents.

What's Included

A2A Server (Transport)

Your network becomes an A2A server:

A2A Client (Connector)

Connect to external A2A servers:

OpenAgents Extensions

We added A2A-aligned methods for network management:

Getting Started

1. Enable A2A

2. Start Your Network

3. Discover Your Agent Card

4. Connect External Agents

What's Next

This is just the beginning of our A2A journey:

Join the A2A Ecosystem

The A2A protocol is open and growing. By adding A2A support, OpenAgents joins a community of interoperable agent frameworks:

Your agents are no longer isolated. They're part of a connected ecosystem.

Resources

Thank You

Thanks to the A2A community and the Linux Foundation for building this open standard. And thanks to our users who've been asking for agent interoperability - this one's for you!

Questions or feedback? Reach out:

Happy connecting!

The OpenAgents Team

Never miss an update

Subscribe and join 100K+ developers building with OpenAgents.

Popular Posts

Image

Hacker News

相關文章

  1. A2A協定解析:AI代理程式如何在系統間進行溝通

    CodiLime · 2 個月前

  2. 概述 - A2A 協議

    a2a-protocol.org · 2 個月前

  3. 完整開發者教學:使用 A2UI 和 A2A 協議建構 AI Agent 使用者介面

    3 個月前

  4. ACP與A2A合併,納入Linux基金會LF AI & Data傘下

    8 個月前

  5. A2UI:Google 針對 AI 代理的聲明式使用者介面協定

    4 個月前