# AirMemo — full discovery file

> AirMemo is governed org memory for AI coding agents: an organization's in-force
> decisions and scoped context, served to agents with provenance and approval
> control. This file is the single-file expansion of https://airmemo.com/llms.txt.

## What AirMemo is

AirMemo keeps an organization's decisions in one place and delivers them into the
agent sessions that need them. A memo is written once, scoped to a team, project,
or the whole org, and delivered into the context of a coding agent on a supported
platform. Deliveries write a receipt: what was delivered, to which agent, on which
platform, and when it expired. Receipts and audit are append-only, so the
receipted count can only go up.

Two properties define the product:

1. Governed, not ambient. Context is an org's official memo set, with provenance
   and approval state, not a scraped pile of notes.
2. Fail-open delivery. The hook checks for an authorized memo on the agent
   lifecycle events the platform already exposes (session start, prompt submit).
   A platform or network failure degrades to memo delayed, never agent blocked.

## The hosted MCP server

AirMemo hosts a Model Context Protocol server over Streamable HTTP.

- Endpoint: https://api.airmemo.com/mcp
- Transport: Streamable HTTP
- Auth: `Authorization: Bearer <org api token>` on every request.

Tools the server registers (five):

- search_context(query, scope?) — ranked search over in-force context (priority,
  then recency). Optional scope filter in `<type>:<ref>` form, e.g.
  `project:payments` or `team:eng`.
- get_decisions(scope?, since?) — the org's in-force decision set. Degrades
  gracefully to the memo set when the decision graph is not populated, and says so.
- get_memo(memo_id) — one memo's body, signature, approval state, scope, author,
  and device delivery chain.
- whoami() — org id, granted scopes, token name and expiry. Use it first to
  confirm connectivity and scope before calling other tools.
- propose_context(title, body, scope, priority?, expiry_min?) — draft a memo into
  the approval flow. This is the only write tool.

## Token and scope model

- An org API token is minted in the portal (Settings → Devices / Tokens).
- Reads require scope `memos:read`.
- `propose_context` additionally requires scope `memos:create`.
- `propose_context` never writes silently: the draft lands with
  `approval_state=pending` and is not in force until an owner or admin approves
  it in the portal.
- The token is sent only in the request header. AirMemo does not log it, and a
  missing, unknown, expired, or revoked token is rejected with HTTP 401
  `invalid_token` before any tool runs.

## Install paths (human-approved, token-authenticated)

Install is two decisions by two people: a requester can point an agent at the
endpoint, and an admin approves the device. AirMemo never writes a client's MCP
config without a click, and nothing installs silently.

1. Get an org. Open one at the console (https://airmemo.com/app) or start at the front desk
   (https://airmemo.com/talk).
2. Mint an org API token in the portal.
3. Add the MCP server to your client, using the endpoint and the token in the
   `Authorization` header. The install page (https://airmemo.com/connect) carries the exact
   per-client command, and the portal's token page shows the same snippet.
4. Approve the device in the portal. The device lands pending; an owner or admin
   approves it, and the seat is counted then. A revoked device frees the seat.

The install page is the canonical walk-through: https://airmemo.com/connect

Command-and-hook installs (the in-repo hook binary) follow the same model. One
binary, one command per platform; the installer merges into a platform's config
file and never overwrites an existing entry.

```bash
airmemo-hook install --platform claude
# claude | codex | copilot | gemini | cursor

airmemo-hook uninstall --platform claude     # removes only AirMemo's entries
```

The binary is not publicly downloadable yet: the repository is still private, so
builds are staged and hash-pinned against SHA256SUMS but there is nothing to fetch
publicly at this time. Per-vendor config files, the events each adapter wires, and
the sample memo tokens are documented at https://airmemo.com/docs.

## Canonical links

- Connect an agent (install + approval): https://airmemo.com/connect
- Docs: the hook, adapters, receipts, enrollment: https://airmemo.com/docs
- Mechanism: how a memo reaches an agent: https://airmemo.com/mechanism
- Security: controls, receipts, and the deferred list: https://airmemo.com/security
- Pricing: the per-agent rate card: https://airmemo.com/pricing
- FAQ: https://airmemo.com/faq
- Terms of Service: https://airmemo.com/terms (raw: https://api.airmemo.com/terms-of-service.md)
- Privacy Policy: https://airmemo.com/privacy
- DPA: https://airmemo.com/dpa (raw: https://api.airmemo.com/data-processing-addendum.md)
- Acceptable Use Policy: https://airmemo.com/aup
- Security & Trust Whitepaper: https://api.airmemo.com/security-whitepaper.md (raw markdown)
- OpenAPI contract: https://api.airmemo.com/docs/openapi.yaml
- Public status (ledger): https://airmemo.com/status
- Changelog (receipt book): https://airmemo.com/changelog