> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fau.run/developer/llms.txt
> Use this file to discover all available pages before exploring further.

# Build an approval app

> Pair with a user’s node, show prompts, decide — without ever holding their mail.

> [!NOTE]
>
> Protocol-developer path: [Build a mobile client](https://docs.fau.run/developer/developers/build-mobile.md). Hub:
> [For protocol developers](https://docs.fau.run/developer/developers.md).

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

| You are building… | You implement… | Start here |
| - | - | - |
| A remote **agent** that asks about mail | Resolve → sign MCP → tools | [Connect your agent](https://docs.fau.run/developer/agents/getting-started.md) |
| An **approval app** (phone, watch, desktop) | Pair → device signing → `/papi/*` → push | This section |

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.

```
Agent  ──MCP──▶  user’s Mac node  ◀──/papi──  your app
                      │
                      └── Gmail / encrypted store (never on your servers)
```

## 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](https://docs.fau.run/developer/apps/signing.md)).
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:

* [Wire specification (fau/1)](https://docs.fau.run/developer/protocol/spec.md)
* [Security model](https://docs.fau.run/developer/protocol/security.md)
* [Device signing vectors](https://docs.fau.run/developer/reference/device-signing.md)

## Reference implementations (optional)

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

| Path | What it is |
| - | - |
| `apps/phone/` | React Native / Expo approval app |
| `apps/macos/` | Menu bar + node supervisor |

## Next

* [App quickstart](https://docs.fau.run/developer/apps/quickstart.md) — pair, list pending, decide
* [Pairing](https://docs.fau.run/developer/apps/pairing.md) — QR payload and `POST /papi/pair`
* [Phone API](https://docs.fau.run/developer/apps/phone-api.md) — full `/papi/*` surface
* [Push notifications](https://docs.fau.run/developer/apps/push.md) — your Expo/APNs credentials, node only stores tokens
* [App checklist](https://docs.fau.run/developer/apps/checklist.md) — ship bar


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.