SDK Playground

Frontend app protocols — wizard, simulator, playground.

• Protocol ID — sdk-playground
• Category — Ecosystem
• Endpoint — POST /api/playground/compute
• Auth — none
• Rate limit — 5/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Interactive API playground. Demo key for testing compute, lattice, shift, and solve without authentication.

Signature

Request

POST /api/playground/compute

Param	Type	Required	Default	Description
domain	string		—	Domain name.
operators	array		—	Operator IDs.
inputs	object		—	Numeric inputs.

Response

{ zeqState, result, meta, zeqProof }

Runnable example

curl -sS -X POST \
  -H "Content-Type: application/json" \
  -d '{
  "domain": "<value>",
  "operators": [],
  "inputs": {}
}' \
  "https://api.zeq.dev/api/playground/compute"

Integrate

1. Domain solver — compose with KO42 + two additional operators from the matching family for pulse-coherent results.
2. Digital twin — pipe sensor data into this protocol every Zeqond to keep the model phase-locked with the system.
3. Alert threshold — flag results whose error_pct exceeds 0.1% as out-of-spec events for the operations layer.

Seeds

• Near — wrap /api/playground/compute in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating SDK Playground alongside a real workload, with pulse-aligned metrics.
• Far — propose SDK Playground as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.