Skip to main content
Protocol-developer path: Build a mobile client. Hub: For protocol developers.
Federated Agent Use is not only for remote AI assistants. You can ship your own phone or desktop app that pairs with a user’s Mac node and becomes the place they approve (or deny) agent requests. Mail still never leaves their laptop. Your app sees only what an approval prompt contains — who is asking, what they want, and for a send prompt, that one draft.

Two developer audiences

Agents and apps meet at the node. Agents call POST /mcp. Apps call /papi/*. The node holds grants, the encrypted store, and the audit log.

What you must get right

  1. Pair once with a one-time code from the Mac setup QR — you get a device_id and you store an Ed25519 key that only this install holds.
  2. Sign every call after pair with that device key (Device signing).
  3. Never trust push payloads for content or action. Push is a wake signal. Fetch the real approval over a signed GET /papi/pending (or open by id after refresh).
  4. Deny is easy. Rejecting must be one tap; allowing must never be the default.

Contracts (public)

Normative text lives in this documentation site:

Reference implementations (optional)

First-party clients illustrate UX; they are not the only legal clients:

Next