POST /api/zeq/operator-spec
The accepted INPUT KEYS for an operator or domain — what zeq_find_operator's description promises.
Call it BEFORE zeq_compute instead of guessing a key name: a guessed key plus (until today) a silent default is how GR37
| Method | POST |
| Path | /api/zeq/operator-spec |
| Feature area | Zeq core & solvers |
| Tag | Zeq Core |
| Auth | public (no key) |
| Tier | computation (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
| Status | Meaning |
|---|---|
200 | OK |
400 | Bad request — a parameter or body field is missing or malformed |
404 | Not found |
400 body
| Field | Type | Required | Description |
|---|---|---|---|
ok | boolean — one of false | yes | — |
error | string | no | Human-readable message. |
code | string | no | Stable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED. |
404 body
| Field | Type | Required | Description |
|---|---|---|---|
ok | boolean — one of false | yes | — |
error | string | no | Human-readable message. |
code | string | no | Stable machine-readable code, e.g. ADMIN_REQUIRED, INVALID_ZID, ZID_NOT_LINKED. |
Call it
curl -sS -X POST https://zeq.me/api/zeq/operator-spec \
-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.