API overview
STATIC exposes a local control API on a separate listener from browsing traffic. someguy and CLI operators use it to inspect readiness, retrieve the public CA certificate, read and select profiles, view a recent telemetry snapshot, and request shutdown. The API does not proxy browsing requests.
The API and the certificate provider are different responsibilities: the provider generates and stores the CA key and issues site certificates; the API lets a local caller inspect or initialize the public CA certificate. The CA and trust guide explains custody and host trust. The control endpoint reference defines the routes.
Endpoint groups
| Group | Routes |
|---|---|
| Lifecycle | GET /status, POST /stop |
| Certificates | GET /ca/status, POST /ca/init |
| Profiles | GET /profiles/catalog, GET /profiles/active, POST /profiles/select, POST /profiles/validate |
| Observability | GET /telemetry/snapshot |
The port is the configured proxy listener port plus two. If a nonempty control.token_path is configured, send X-404-Control-Token on every request. Keep this listener on loopback; without a configured token the implementation performs no token check. See Control endpoints for route behavior and control.rs for source definitions.
Next in this section
Continue to Control endpoints for request/response shapes, authentication and the distinction between listener readiness and browser coverage.