A2A Agent Card Generator
Build a Google A2A (Agent2Agent) Agent Card JSON manifest — name, capabilities, input/output modes, and skills — served at the well-known agent-card.json path. Copy-ready.
What this tool does
In Google A2A (Agent2Agent), every agent publishes an Agent Card: a small JSON manifest that other agents read to discover what it can do and how to reach it. This generator builds a valid Agent Card from a simple form, so you do not have to hand-write the JSON.
What goes in an Agent Card
- Identity: the agent name, a description, its URL, and a version.
- Provider: the organization behind the agent and its URL.
- Capabilities: flags such as streaming, push notifications, and state transition history.
- Modes: the default input and output content types the agent accepts and returns, such as text or application/json.
- Skills: a list of what the agent can do, each with an id, a name, a description, tags, and example prompts.
How to use it
- Fill in the identity, provider, and version fields.
- Check the capabilities your agent supports.
- Choose the default input and output modes.
- Add one or more skills.
- Copy the generated JSON.
Where the Agent Card lives
By convention, an Agent Card is served at the path /.well-known/agent-card.json on the agent base URL. Other agents and registries fetch it there to discover your agent.
Related
To understand where A2A fits among MCP and the other agent protocols, read our guide to AI agent protocols. A2A handles agent-to-agent collaboration, while MCP connects an agent to its tools.
You build the idea. I'll ship the product.
Productized MVP development for founders. 9 SaaS apps shipped — yours could be next, in 6 weeks. Secure by default.
ℹ️ Disclaimer
This tool is provided for informational and educational purposes only. All processing happens entirely in your browser - no data is sent to or stored on our servers. While we strive for accuracy, we make no warranties about the completeness or reliability of results. Use at your own discretion.