Using A2A Protocol Validator to Verify Domain Support for A2A Protocol

Based on the A2A Protocol blog, we learned about the basic concepts of A2A Protocol and how to develop using the A2A Protocol Python SDK.
This article will introduce how to use A2A Protocol Validator to verify A2A Protocol and visualize AgentCard for convenient debugging:
- Verify whether a given domain supports A2A Protocol
- Visualize AgentCard
For publicly deployed A2A Agents, you can directly input the domain for verification.
How to Verify Locally Running A2A Agent?
- Prepare Agent
git clone https://github.com/sing1ee/a2a-python-currency.git
cd a2a-python-currency
uv run python main.py
Output:
Installed 27 packages in 33ms
INFO: Started server process [61455]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://localhost:10000 (Press CTRL+C to quit)
This way, the Currency Agent is running locally, accessible on port 10000.
- Map local Agent service - Using Cloudflare Zero Trust Refer to the documentation for installation. My environment is Mac
brew install cloudflared
- Start Zero Trust proxy
cloudflared tunnel --url localhost:10000
Output:
+--------------------------------------------------------------------------------------------+
2025-06-03T09:03:02Z INF | Your quick Tunnel has been created! Visit it at (it may take some time to be reachable): |
2025-06-03T09:03:02Z INF | https://sheriff-honor-undefined-relate.trycloudflare.com |
2025-06-03T09:03:02Z INF +--------------------------------------------------------------------------------------------+
https://sheriff-honor-undefined-relate.trycloudflare.com is the temporary domain that can access our local Agent service.
Open A2A Protocol Validator
Open A2A Protocol Validator, input the above domain, and you can verify whether the domain supports A2A Protocol.
Through these steps, you can quickly debug. We will launch an A2A online client in the future to make execution more convenient.
Related Articles
Explore more content related to this topic
A2UI Introduction - Declarative UI Protocol for Agent-Driven Interfaces
Discover A2UI, the declarative UI protocol that enables AI agents to generate rich, interactive user interfaces. Learn how A2UI works, who it's for, how to use it, and see real-world examples from Google Opal, Gemini Enterprise, and Flutter GenUI SDK.
Agent Gateway Protocol (AGP): Practical Tutorial and Specification
Learn the Agent Gateway Protocol (AGP): what it is, problems it solves, core spec (capability announcements, intent payloads, routing and error codes), routing algorithm, and how to run a working simulation.
Integrating A2A Protocol - Intelligent Agent Communication Solution for BeeAI Framework
Using A2A protocol instead of ACP is a better choice for BeeAI, reducing protocol fragmentation and improving ecosystem integration.
A2A vs ACP Protocol Comparison Analysis Report
A2A (Agent2Agent Protocol) and ACP (Agent Communication Protocol) represent two mainstream technical approaches in AI multi-agent system communication: 'cross-platform interoperability' and 'local/edge autonomy' respectively. A2A, with its powerful cross-vendor interconnection capabilities and rich task collaboration mechanisms, has become the preferred choice for cloud-based and distributed multi-agent scenarios; while ACP, with its low-latency, local-first, cloud-independent characteristics, is suitable for privacy-sensitive, bandwidth-constrained, or edge computing environments. Both protocols have their own focus in protocol design, ecosystem construction, and standardization governance, and are expected to further converge in openness in the future. Developers are advised to choose the most suitable protocol stack based on actual business needs.
A2A Inspector: A Deep Dive into Agent2Agent Communication Debugging
Learn about the A2A Inspector architecture and implementation - a powerful web-based tool that enables developers to connect to A2A agents, inspect agent cards, validate protocol compliance, and debug JSON-RPC communications in real-time.