Every route the local gateway serves on 127.0.0.1:4320, rendered live from the
OpenAPI contract
the SDKs are generated from — so what you read here is what every SDK can call.
Back to the docs.
Read-only on purpose. The gateway refuses requests from any web origin it was not told to trust — that is what stops a drive-by page from driving your coding agent — so this page cannot "Try it out". Use curl (examples in the docs) or the CLI: chatpanel status, chatpanel ask.
Each operation carries x-chatpanel-auth (open for any local process, token for the per-install token in ~/.chatpanel/gateway-token or a paired copy), x-chatpanel-since (the gateway version that introduced it — check GET /health), and x-chatpanel-stream: sse where the answer is a stream. Admin and destructive routes (/config, /logs, clear history/memory) are deliberately not in the contract.
Chap open — any process on this machine
token — the gateway token, or paired
sse — text/event-stream