A2A Agent Card
Agent-to-Agent interoperability — current status and what exists today.
Status: not yet implemented. As of this writing, JOGL Network does not publish an A2A (Agent-to-Agent) Agent Card. This page documents the current state and the discovery metadata that does exist, so it can be filled in once the Agent Card ships.
What exists today
Agent access to JOGL Network is through the MCP server. The codebase publishes standards-based discovery metadata for MCP OAuth, but not an A2A Agent Card:
- RFC 9728 protected-resource metadata at
/.well-known/oauth-protected-resource/mcp, which points MCP clients at the authorization server (WorkOS AuthKit). This is what lets a one-click OAuth connector discover how to authenticate. - OAuth authorization-server metadata, served by the
oauth-metadataedge function.
There is no A2A Agent Card endpoint (the current A2A discovery path is
/.well-known/agent-card.json, per A2A v0.3.0+; the pre-0.3.0 path was
/.well-known/agent.json), and no A2A skills/capabilities descriptor, in the repository today.
TODO — for the maintainers
To publish an A2A Agent Card, the following need to be decided and provided:
TODO:Should JOGL Network expose an A2A Agent Card at all, or is MCP the sole agent interface for now?TODO:If yes: the Agent Card contents —name,description, serviceurl, provider, supportedcapabilities,skills(likely mirroring the MCP tools: search, member reads, enrichment), authentication schemes (reuse the OAuth/API-key model), and the canonical hosting URL for/.well-known/agent-card.json.TODO:Whether A2A skills map 1:1 to the existing MCP tools or expose a higher-level surface.
Once those are settled, this page should document the Agent Card and link to the live
.well-known endpoint.