Local SDK

Run Zeq on your own hardware — single-file clients in Python, JavaScript, Go, Rust, and curl, full source pasted in-page.

Every Zeq SDK is a single file, fully auditable, and pasted in-page so you can read the math before you run it. Pick a language, copy the client, point it at the Zeq API — or at your own backend. The v1.1.3 wire contract is the same either way.

Languages

Python verified live

Online client + the full 1047-line offline HULYAS reference implementation.

Open Python SDK

JavaScript / Node verified live

Zero-dep fetch client; works in Node 18+ and modern browsers.

Open JavaScript SDK

Go

Single-file stdlib-only client. go run it.

Open Go SDK

Rust

Single-file ureq + serde. Cargo-ready.

Open Rust SDK

curl / bash verified live

One-line wrapper for CI, Makefiles, quick checks.

Open curl SDK

Why we paste the source

Why inline? The full SDK source is pasted below so the mathematics is auditable. Copy-paste it, read it, self-host it — you never have to trust the Zeq API as a black box. Use our key for convenience, or wire it into your own backend. The v1.1.3 binding contract and ZeqProof HMAC are identical either way.

The API runs the same 42-operator Kinematic spectrum and KO42.1/KO42.2 tensioners that the offline hulyas_framework.py runs. You can run the offline framework locally, post the same inputs to the online API, and compare the two — they agree to ≤0.1 %. This is the transparency guarantee. Zeq is not a black box.

Proof of verifiability

# Both paths compute the SAME physics:

# Path A — online
curl -H "Authorization: Bearer $ZEQ_TOKEN" \
     -d '{"operator_id":"NM21","inputs":{"m1":5.972e24,"m2":7.342e22,"r":3.844e8}}' \
     https://www.zeq.dev/api/zeq/compute
# → value: 1.98049e20, solver: "operator:NM21"

# Path B — offline (air-gapped)
python3 -c "
from hulyas_framework import compute_operator_nm21
print(compute_operator_nm21(m1=5.972e24, m2=7.342e22, r=3.844e8))
# → 1.98049e20
"