GET/api/statsThe live snapshot: links, peers, routes, topology with positions, crypto posture, QoS counters, bonding tax.
GET/api/interfacesEvery daemon instance on the host.
GET/api/scheduler-logRecent scheduler decisions — timestamp, strategy, chosen links, costs. “Why did it pick the serial radio there?” is answerable after the fact.
GET/api/qosLive class policy + per-class counters and escalation state.
PUT/api/qosMerge-update the policy at runtime — no restart.
GET/api/netcheckPer-link public endpoints and NAT classification from the last netcheck.
PUT/api/positionOperator position inject — persisted, validated, picked up within an advertisement tick.
GET/api/config · /api/config/schemaThe live TOML (secrets redacted, comments preserved) and its schema.
POST/api/config/validate · stage · commit · confirm · revertThe commit-confirmed lifecycle, exactly as described above.
GET/api/config/apply-status · /api/config/epochThe apply state machine the countdown UI polls; the current epoch envelope + per-node fleet status.
GET/api/config/rollout · /api/config/rolloutsThe live rollout with both gates — the canary gate and the release gate with its required, confirmed, silent and failed counts, the deadline and an abort cause when there is one — plus the timeline; and the archive of past rollouts. update classes ↗
POST/api/config/rollout/start · release · abortStart a canary rollout (release_watch_secs sets this rollout’s release deadline), sign the release, or sign the baseline forward. An abort may also end a released rollout still waiting on a required node.
POST/api/fleet/update-classSet a record’s update class and sign the next fleet list with this node’s config-author key (409 without one). A write-scope token may call it.
GET/api/fleet/rotationsEvery rotation schedule with its three instants, each node’s reported state for it, the retire gate, and the nodes still on the old key or secret. rotation ↗
POST/api/fleet/rotations · /api/fleet/rotations/<id>/activate · retire · cancelPlan a rotation (kind, subject, windows) and sign it into the list; bring activation forward; sign the retire step, refused while a required node has not reported active unless forced, which is recorded; cancel before activate. These take a session; a write-scope token reaches only update-class.
POST/api/config/pushSign the live file’s policy sections as the next epoch and hand it to gossip (409 with a hint when no author key exists).
GET/api/admission · /api/admission/pending · /api/admission/invitesWho is knocking, who is blocked, the open invitations and who used them, the records held outside the signed list. admission modes ↗
POST/api/admission/invites · approve · deny · unblockMint a pairing code, decide on a knocking key or a record another node forwarded, lift a block — callable with a write token, so a platform backend runs admission without a human session.
POST/api/fleet/revokePreview, then sign and push a removal: the records revoked, the mesh secret rotated, the list flooded. removal ↗
POST/api/fleet/select-areaA polygon in, the review out: the records whose last advertised position lies inside, each with the age of its fix, a count of those outside, and the records with no position. Selects only; the removal is /api/fleet/revoke. removal by area ↗
POST/api/fleet/zeroizePreview, sign and push a remote zeroize for one node, held until a set time if asked, or cancel a pending one. The command also revokes the node. Signs with this node’s config-author key and refuses the node it runs on. All three fleet writes take a write-scope API token as well as a session. remote zeroize ↗
POST/api/auth/login · logout · webauthn/*Session and FIDO2 ceremonies for the dashboard’s local accounts.