Skip to main content

Your first compute

With a key in hand, compute something real and then prove it to yourself. This isn't a lookup — the number is derived from r_s = 2GM/c² with bound CODATA constants, and it comes back with everything you need to check it.

Compute​

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}}'

Returns 2954.0077 m — the Schwarzschild radius of the Sun — with the equation it used, the constants it bound, an uncertainty, and a signed envelope. Swap the operator and it's a different science: MED_BMI {mass:70,height:1.75} → 22.857 kg/m², BLACK_SCHOLES {S:100,K:100,r:0.05,T:1,sigma:0.2} → 10.4506.

Verify​

The point of Zeq is that you don't have to trust that number. Hand the returned proof to a verifier — on any node — and it re-checks independently:

zeq verify   # or POST the envelope to /api/zeq/verify

Same equations, same constants, same bits on every node: the verifier re-runs the maths and re-checks the stamp without trusting the machine that produced it. That round-trip — compute anywhere, verify anywhere — is the whole framework in miniature.

What just happened​

Your call ran the seven-step pipeline: operator selection, constant binding, dimensional validation, the actual float64 evaluation, a precision check, a clock stamp, and a signed return. Nothing was fabricated, and every step is visible in the envelope.