Language SDKs
Every SDK is a thin, typed wrapper over the same wire protocol — so whichever language you reach for, you get the same constants, the same equations, and the same Ed25519-signed result you can verify offline. The clients differ only in ergonomics, never in the physics.
The flagship — @zeq/sdk (TypeScript / JavaScript)
A typed client for your hosted machine — HulyaPulse timing, the operator catalogue, and the
platform calls in one package, all computing on our nodes. It's published to Zeq's own registry
(not npmjs), so you point the @zeq scope at it once, then install normally:
npm config set @zeq:registry https://zeqsdk.com/registry
npm install @zeq/sdk
It's a typed client for your hosted machine — it calls the framework on our nodes and hands you back signed results. It can also compute and verify offline with no secrets where that helps (the same verification any node performs), but the default path is the hosted compute you subscribe to.
Python — zeq.py, no pip
A single file, fetched straight from a node — nothing to install into your environment:
curl -fsSO https://zeqsdk.com/cli/zeq.py
Built for data-science workflows — Jupyter, NumPy pipelines — where you want verified physics inline with the rest of your analysis.
Every client
| Client | How you get it | Best for |
|---|---|---|
TypeScript / JavaScript — @zeq/sdk | npm install @zeq/sdk (Zeq registry) | apps, services, notebooks — the flagship |
Terminal CLI — zeq | install.sh | first install, tutorials, zeq verify |
Python — zeq.py | curl one file, no pip | data science, Jupyter, NumPy |
| HTTP / curl | nothing to install — the wire format itself | any language; the protocol every client speaks |
| Go · Rust · Java · Kotlin · Swift · Ruby · C++ | from the Zeq registry | native clients in your stack |
| MCP server | @zeq/mcp | AI agents — tool use |
| Kernel skill | served by every node | teaching an agent the kernel contract |
HTTP is the floor
Under all of them is plain HTTP — the wire format is the SDK. Anything that can make a request can
speak Zeq, and every worked example in these docs is a curl you can run as-is. The typed SDKs exist
to make that pleasant in your language, not to gate it behind one.
Read next
- The terminal CLI — the fastest install.
- The reference — every endpoint the SDKs wrap.
- Proofs — the offline verification every client can do.