Fleet

17 live operations under /api/fleet. 9 require a machine key; 8 are public. Tagged: Mesh & Nodes.

Method	Path	What it does	Auth
POST	/api/fleet/{slug}/govern	1. Propose	key
POST	/api/fleet/{slug}/invite	1. POST /api/fleet/:slug/invite	key
GET	/api/fleet/{slug}/parties	—	key
POST	/api/fleet/governance/{id}/approve	3. Approve, with an equation proof	key
POST	/api/fleet/governance/{id}/cancel	4. Withdraw	key
GET	/api/fleet/governance	2. What is waiting for MY equation	key
POST	/api/fleet/invites/{id}/accept	—	key
GET	/api/fleet/invites	2. GET /api/fleet/invites Invitations addressed to ME.	key
GET	/api/fleet/nodes	—	public
GET	/api/fleet/placement	—	public
POST	/api/fleet/reconcile	—	public
GET	/api/fleet/replicas	—	public
GET	/api/fleet/route	—	public
POST	/api/fleet/spine/verify	Phase 6 — verify a seal in isolation (genesis prevY for index 0, else supplied).	public
POST	/api/fleet/spine/witness	Phase 6 — ingest a peer's seal head: verify the VDF + record it (the HTTP cross-anchor path; the mesh delivers the same	public
GET	/api/fleet/spine	Phase 6 — the fleet's cross-witnessed VDF spine (peers' verified seal heads).	public
GET	/api/fleet	—	key

Generated by scripts/generate-reference.mjs from https://zeq.me/openapi.json.