Protocol-developer path: Build a mobile client. Hub:
For protocol developers.
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
- Pair once with a one-time code from the Mac setup QR — you get a
device_idand you store an Ed25519 key that only this install holds. - Sign every call after pair with that device key (Device signing).
- 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). - 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
- App quickstart — pair, list pending, decide
- Pairing — QR payload and
POST /papi/pair - Phone API — full
/papi/*surface - Push notifications — your Expo/APNs credentials, node only stores tokens
- App checklist — ship bar