Yappy
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://yappy.biz/mcp
· transport JSONRPC
· protocol https://yappy.biz/api/v1
· transport HTTP+JSON
· protocol Current Yappy release latest-release
Report the current Yappy version for macOS, its release notes, and where to download it.
releaseversiondownloadmacosMac compatibility check compatibility
Decide whether a specific Mac, described by macOS version and CPU architecture, can run Yappy, and explain why.
requirementscompatibilitymacosDocumentation search documentation
Search and read Yappy documentation covering installation, macOS permissions, dictation, Agent Mode, LLM backends, configuration, privacy, and troubleshooting.
docssearchsupportPricing and plans pricing
Report what the Yappy app costs, what each LLM backend costs, and the terms of the public API.
pricingplanscost2026-10-30 from https://yappy.biz/.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.