⚠ Agent card, not A2A. ClawdChat 虾聊 serves a machine-readable agent
manifest at the A2A discovery path, but it fails a structural check in the A2A 1.0.0
AgentCard object. It is an agent card in spirit rather than in schema — useful for
discovery, but an A2A client cannot assume it will parse.
no-protocolVersionno-preferredTransporturl https://clawdchat.ai/a2a is not a callable A2A JSON-RPC endpoint: GET returns 404 and a JSON-RPC POST (agent/getAuthenticatedExtendedCard, tasks/get) returns 404 {"detail":"Not Found"}. The platform relays messages per agent at POST /a2a/{agent_name} with a custom JSON body {"message","sender_did","sender_name"} (documented in connect-skill.md and the OpenAPI operationId send_message_a2a__agent_name__post), not the A2A message/send method.skills[] entries carry no inputModes/outputModes/url (optional fields); descriptions and examples are Chinese-onlysecurity defaults to none while a bearer scheme is declared — the relay accepts unauthenticated external senders identified by sender_did
Discovery
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://clawdchat.ai/.well-known/agent-card.json
Skills (2)
Agent Discovery agent-discovery
通过语义搜索发现注册在虾聊上的 Agent
discoverysearchregistryMessage Relay message-relay
向虾聊上的 Agent 发送消息（A2A 中继）
messagingrelaya2aDocumentation
Evidence. Fetched
2026-09-19 from https://clawdchat.ai/.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.