Gateway Protocol ← Back to gateway

For developers

Network & API reference

Gateway Protocol is sovereign on the desktop and works fully offline. This server adds an optional, anonymous, in-memory network layer — a small REST + WebSocket surface. No accounts, no cookies, nothing persisted to disk.

App & status

GET/Marketing landing for browsers; health JSON for API clients (content-negotiated on Accept).
GET/appThe installable web app (PWA).
GET/versionLatest desktop version — drives the in-app update banner. Returns { version, releasedAt, notes, downloadUrl }.
GET/manifest.webmanifestPWA manifest; plus /sw.js, /qr-app.svg, /icons/*.

Downloads

GET/downloadmacOS disk image (.dmg), baked into the deploy.
GET/download/windows302 → latest Windows installer on the GitHub Release.
GET/download/linux302 → latest Linux package on the GitHub Release.

Transmission feed

GET/feed?wave=&code=&limit=List anonymous transmissions. limit defaults to 50 (max 200); optional filter by wave or activation code.
POST/feedPublish a transmission. Requires the X-Gateway-Client header (CSRF guard); rate-limited per IP.
POST/feed/:id/reactAdd a +1 reaction to a transmission.

Practice rooms

WSS/room/:codeJoin a live-synchronized room (code = 4–12 alphanumerics). First joiner hosts the timer + phase; everyone else mirrors it. Anonymous presence count only — no chat, no identifiers.

Optional LLM/TTS relay (PWA / mobile)

GET/api/status · /byok/statusRelay availability for the managed (server-key) and bring-your-own-key paths.
POST/api/anthropic/messagesManaged Council relay, only if a server key is configured.
POST/byok/anthropic/messagesBring-your-own-key relay — your key is proxied per-request, never stored.

Conventions

Gateway Protocol · Reference Server · v3.3.5 · build d7c9c9e