SaaSHub helps you find the best software and product alternatives Learn more →
Top 21 Python a2a Projects
-
Project mention: Show HN: An open-source communication layer for AI agents | news.ycombinator.com | 2026-01-13
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
solace-agent-mesh
An event-driven framework designed to build and orchestrate multi-agent AI systems. It enables seamless integration of AI agents with real-world data sources and systems, facilitating complex, multi-step workflows.
Project mention: Ditch the Monolith: Build Scalable AI Teams with Solace Agent Mesh | dev.to | 2025-10-10View the Project on GitHub
-
AG2 (formerly AutoGen) changes that. It provides a shared runtime where specialized agents with defined roles, tools and conversation patterns can collaborate as one coordinated team across models and even frameworks.
-
Project mention: Show HN: Delegare – let AI agents pay safely (x402, AP2 – base/USDC and Stripe) | news.ycombinator.com | 2026-04-28
c) similar workaround e.g. pre-funded wallets
So I started building out a solution. For my use case it was important to not only have stablecoins but also a fiat rail which is now implemented using Stripe.
Initially I build a mandate system internally but am very glad and big shoutout to the guys at google for AP2 (https://github.com/google-agentic-commerce/AP2) which I ended up using for the scoped payment mandates.
Please do check it out and would appreciate feedback from people building in the space.
Docs:
-
Project mention: How to use a2a-python to Create and Connect Github Agent with Google's Agent-to-Agent (A2A) Protocol | dev.to | 2025-06-17
A2A SDK - The underlying A2A protocol implementation
-
Project mention: Implementing Adversarial Agent Simulation System with A2A and AnyAgent | dev.to | 2025-08-12
This example uses the any-agent library, which has built-in support for providing agent services through the A2A protocol. Documentation for service options can be found here. Using any-agent, you can control the LLM models used by the agent and defender, as well as the agent framework used.
-
bernstein
Audit-grade multi-agent orchestration for CLI coding agents (Claude Code, Codex, Gemini CLI, +40 more). HMAC-chained audit log, signed agent cards, per-artefact lineage, air-gap deploy. The orchestrator your compliance team will sign off on. https://bernstein.run
Project mention: bernstein 2.x recap: lineage, ten trackers, A2A capability cards, and a CI that started fixing itself | dev.to | 2026-05-20#1720 — Skills end-to-end. The skill subsystem already has discovery, layered merge (BASE / TEAM / USER under XDG, above), and an injector for Claude Code. The operator never touches it because there is no install, no sync, no publish, no lint, no test, no init, no watch. If you have an opinion on the verb surface, the manifest shape, or whether a community index belongs in scope at all, the RFC is where to leave it.
-
a2a-x402
The A2A x402 Extension brings cryptocurrency payments to the Agent-to-Agent (A2A) protocol, enabling agents to monetize their services through on-chain payments. This extension revives the spirit of HTTP 402 "Payment Required" for the decentralized agent ecosystem.
Project mention: x402 — An open protocol for internet-native payments | news.ycombinator.com | 2025-09-23https://github.com/google-a2a/a2a-x402
SingularityNET is this concept too, FWIU.
So A2A has W3C VC Verifiable Credentials (and DIDs), but not x402?
Re: ILP payment pointers, DNS, blockerts (W3C VC) https://news.ycombinator.com/item?id=42961635 :
> How can or should a Blockcert indicate an ILP Interledger Protocol address or a Payment Pointer?
In order to avoid DNS. Basically because gethostbyname() does not indicate DNSSEC validation status, or channel sec status e.g. whether there's DoH/DoT/DoQ at every edge in the DNS network), or CT Certificate Transparency log cert revocation status (and OCSP and CRL are in-band))
How can ILP and x402 (and IDK EDNS) be integrated? Are they complementary?
> Think of x402 as the universal "cash register" signal and ILP as the versatile "payment network" that can handle any currency. [...] and pathfinding with path cost and HTA Hashed-Timelock Agreements for the whole path, with an auditable open spec message standard that accounts for each of the Connectors involved (who specify credit limits).
> So, x402 can signal the need for a payment, and ILP can be the underlying mechanism to fulfill that payment request, regardless of the user's preferred currency or payment provider
How do x402 and ILP SPP Simple Payment compare in terms of signaling the need for a payment?
> SPP is a simplified, connectionless mode of Interledger that is often used for streaming micropayments, as seen in the Web Monetization standard. The signaling is more implicit and is discovered through HTML/HTTP, rather than being an HTTP status code itself.
There's probably a better HTTP Status dog for 402?
-
dns-aid-core
DNS-based Agent Identification and Discovery - Reference Implementation for IETF BANDAID
Project mention: DNS Is Becoming the Discovery Layer for AI Agents: What DNS-AID Means for Your Infrastructure | dev.to | 2026-06-03The reference implementation, developed by Infoblox and hosted under the Linux Foundation, already supports publishing, discovery, verification, and invocation across multiple DNS providers including Route 53, Cloudflare, NS1, Google Cloud DNS, and BIND via RFC 2136.
-
Project mention: Show HN: Handler – A2A Protocol Client CLI and TUI | news.ycombinator.com | 2025-12-07
-
-
AgentVault
"Open-source toolkit (Python Library, Registry API, CLI) for secure, decentralized AI agent interoperability using A2A/MCP."
-
Project mention: Show HN: Running local OpenClaw together with remote agents in an open network | news.ycombinator.com | 2026-04-04
-
AWAS
Open-source standard for AI-readable web actions - enabling AI browsers to interact with websites efficiently
Project mention: Show HN: AWAS – An open standard for AI-readable web actions | news.ycombinator.com | 2025-11-30 -
piqrypt
AI agent governance layer — sign, monitor and control every agent action. EU AI Act · ANSSI · NIST ready.
Full demo code: github.com/piqrypt/piqrypt/demos
-
Full TechSpec (Section 8.8): moltrust.ch GitHub: github.com/MoltyCel/moltrust-protocol
-
-
mcpkernel
The Security Kernel for AI Agents — MCP/A2A gateway with policy enforcement, taint tracking, sandboxed execution, deterministic envelopes, and Sigstore audit. OWASP ASI 2026 compliant.
GitHub: github.com/piyushptiwari1/mcpkernel
-
lucy-agent
AI agent for writing, research, code, DeFi & blockchain. Pay per task in USDC on Base or Solana. A2A + MCP + x402 protocols.
Project mention: Lucy – pay-per-task AI agent in USDC, no subscription (A2A/MCP/x402) | news.ycombinator.com | 2026-05-22 -
a2a_llama_index_file_chat
This sample demonstrates a conversational agent built with LlamaIndex Workflows and exposed through the A2A protocol. It showcases file upload and parsing, conversational interactions with support for multi-turn dialogue, streaming responses/updates, and in-line citations.
Python a2a discussion
Python a2a related posts
-
Hermes Agent – Open-Source AI Agent with Persistent Memory
-
Nous Research edits GitHub issue to remove plagiarism claims about Hermes Agent
-
Show HN: Delegare – let AI agents pay safely (x402, AP2 – base/USDC and Stripe)
-
How we made MolTrust A2A v0.3 conformant
-
Two of Three: MolTrust Closes RSAC 2026's Open Agent Security Gaps
-
Give Your AG2 Agents a UI with AG‑UI and CopilotKit
-
The Code-Only Agent
-
A note from our sponsor - SaaSHub
www.saashub.com | 9 Jun 2026
Index
What are some of the best open-source a2a projects in Python? This list will help you:
| # | Project | Stars |
|---|---|---|
| 1 | Bindu | 6,806 |
| 2 | solace-agent-mesh | 4,784 |
| 3 | ag2 | 4,638 |
| 4 | AP2 | 3,053 |
| 5 | a2a-python | 1,952 |
| 6 | any-agent | 1,174 |
| 7 | bernstein | 547 |
| 8 | a2a-x402 | 521 |
| 9 | dns-aid-core | 42 |
| 10 | Handler | 41 |
| 11 | a2a-langgraph | 27 |
| 12 | AgentVault | 16 |
| 13 | hybro-hub | 14 |
| 14 | a2a-mcp-openrouter | 7 |
| 15 | AWAS | 5 |
| 16 | piqrypt | 3 |
| 17 | moltrust-api | 3 |
| 18 | a2a-python-currency | 2 |
| 19 | mcpkernel | 1 |
| 20 | lucy-agent | 0 |
| 21 | a2a_llama_index_file_chat | 0 |