Skip to main content

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 events automatically).

MethodPOST
Path/api/fleet/spine/witness
Feature areaFleet
TagMesh & Nodes
Authpublic (no key)
Tiercomputation (public)

Parameters

This operation publishes no path, query or header parameters.

Request body

Optional. Content type: application/json.

The node publishes this body as a free-form JSON object — no field schema is exposed in openapi.json. Send the fields the summary above describes; the endpoint validates them and refuses rather than guessing.

Responses

StatusMeaning
200OK
400Bad request — a parameter or body field is missing or malformed

400 body

FieldTypeRequiredDescription
okboolean — one of falseyes
errorstringnoHuman-readable message.
codestringnoStable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED.

Call it

curl -sS -X POST https://zeq.me/api/fleet/spine/witness \
-H "Content-Type: application/json" \
-d '{}'

Generated from the live OpenAPI description (https://zeq.me/openapi.json, spec version 1.287.0) by scripts/generate-reference.mjs. Do not edit — this file is rewritten on every run.