A2A Agent Card · Zephyr Cloud
Zephyr Cloud Agent
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://zephyr-cloud.io/.well-known/agent.json
Skills (3)
Start onboarding start-onboarding
Route a user into Zephyr Cloud onboarding and setup.
Explore docs explore-docs
Send developers to the Zephyr Cloud documentation.
Review pricing review-pricing
Open Zephyr Cloud pricing for plan comparison.
Documentation
Evidence. Fetched
2026-10-29 from https://zephyr-cloud.io/.well-known/agent.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.