`POST /api/zeq/compliance/verify`

Pure crypto — does NOT touch the DB, does NOT validate the proof against the issuing key (that's /api/zeq/verify's job for the original caller). What this proves: the envelope hasn't been altered since it was sealed.


Method	`POST`
Path	`/api/zeq/compliance/verify`
Auth	public (no key)
Group	Compute · Zeq

Request

curl -X POST https://zeqsdk.com/api/zeq/compliance/verify \
  -H "Content-Type: application/json" \
  -d '{ }'   # request body — see description

Generated from the node's own route registry (GET /api/endpoints) — this path is live.

Request​

Request