Skip to main content

Start here

Two commands, no signup — a real physics result you can verify.

1 — Mint a free key​

curl -sX POST https://zeqsdk.com/api/demo-key/mint
# → { "key": "zeq_ak_demo_…", "plan": "demo", "computeBudget": 5 }

A demo key is five real computes — no card, no signup — enough to feel the whole surface.

2 — Compute something real​

The Schwarzschild radius of the Sun, derived — not looked up. The key computes immediately; there's nothing to set up first:

ZEQ_KEY=$(curl -sX POST https://zeqsdk.com/api/demo-key/mint | jq -r .key)

curl -sX POST https://zeqsdk.com/api/zeq/compute \
  -H "Authorization: Bearer $ZEQ_KEY" \
  -H "Content-Type: application/json" \
  -d '{"operators":["KO42","GR37"],"inputs":{"mass":1.98892e30}}'
# → 2954.0077 m

Returns 2954.0077 m — with the equation it used (r_s = 2GM/c²), the CODATA constants it bound, an uncertainty, and a signed envelope. Swap the operator for a different science: MED_BMI {"mass":70,"height":1.75} → 22.857 kg/m², or BLACK_SCHOLES {"S":100,"K":100,"r":0.05,"T":1,"sigma":0.2} → 10.4506.

What just happened​

Your query ran the seven-step pipeline — operator selection, constant binding, dimensional validation, a closed-form solver, a precision check, a clock stamp, and a signed return. Read how it computes to see each step.

3 — Spin up your own machine​

The demo key is for trying it. When you want a machine that's yours — a persistent backend with its own keys, audit chain, and clock, plus the 1,287-credit welcome — spin one up in the browser:

Spin up your machine — free See the live nodes

You create a free account and your recovery equation is shown once — save it, there's no password reset. Then walk the path in depth:

  1. Spin up your machine — how it works, and saving your recovery equation.
  2. Your first compute — run one on your machine and read the whole signed envelope.
  3. Deploy your first contract — put standing logic inside a machine, verified live.

How these docs are written​

Every section of this site follows one rule: generated from or verified against the live system. The reference is built from the node's own registries; every worked example prints a number you can reproduce with the command shown.