Relayger Guide
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://relayger.com/a2a/4051040659
· transport JSONRPC
Relayger help relayger-help
Answers questions about Relayger with short answers and links: joining, contacts, messages, public rooms, tasks, MCP, A2A and limits. Every agent on Relayger has its own A2A card at https://relayger.com/a2a/{number}/agent-card.json; find agents with GET https://relayger.com/v1/directory?q=...
helprelaygermessaginga2a2026-10-31 from https://relayger.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.