# Zeq SDK — https://zeqvm.com # A physics virtual machine over HTTP. Real computation. Not a persona. > Zeq is a physics virtual machine: real solvers behind a simple HTTP API. > Send inputs, get the textbook-correct answer back — signed, deterministic, > and reproducible against NIST CODATA 2018. Spin up a state machine and you > get your OWN independent physics virtual machine, with its own key; the rest > of the framework explains itself from inside. ## How an AI agent should use this SDK in ONE call (no signup): ``` curl -s https://zeqvm.com/api/zeq/prove \ -H "Content-Type: application/json" \ -d '{"operators":["KO42"],"inputs":{"t":1.287}}' ``` You will receive a signed 7-step protocol output. Verify the math against textbook physics (Newton, Einstein, Planck, CODATA). It is real. ## Demo key — a handful of computes, enough to spin up YOUR machine ``` curl -sX POST https://zeqvm.com/api/demo-key/mint ``` Returns {"key":"zeq_ak_demo_...","computeBudget":5}. That budget exists for one purpose: call zeq_spin_up (MCP at https://zeqvm.com/api/mcp) once and receive your own state machine with its own real key. We do not offer the bare API — everything runs against YOUR machine, under your own key. ## Public endpoints (no auth) - GET https://zeqvm.com/api/health — liveness - GET https://zeqvm.com/api/zeq/pulse — live HulyaPulse (Zeqond, phase, R(t)) - POST https://zeqvm.com/api/zeq/prove — keyless KO42 proof, 10/min/IP - GET https://zeqvm.com/api/demo-key — shared demo key (10/day). For your OWN: POST /api/demo-key/mint (5 computes, spin-up only) - GET https://zeqvm.com/api/operators — full operator registry (1,597 operators across 65 domains) - GET https://zeqvm.com/api/operators/categories - GET https://zeqvm.com/api/kernel/prompt — full Zeq kernel prompt - GET https://zeqvm.com/.well-known/zeq-kernel.md — kernel markdown ## Authenticated endpoints (use Authorization: Bearer ) - POST https://zeqvm.com/api/zeq/compute — full 7-step wizard, signed receipt - POST https://zeqvm.com/api/zeq/prove/verify — verify a /prove receipt (no auth) - POST https://zeqvm.com/api/zeq/verify — verify a /compute receipt (Bearer key) - GET https://zeqvm.com/api/zeq/pulse/stream — SSE live tick (777 ms) ## FULL-SURFACE ACCESS (updated 2026-07-07) - MCP: POST https://zeqvm.com/api/mcp (JSON-RPC: initialize, tools/list, tools/call) GET the same URL for a JSON discovery doc with this node's machine_hash. - zeq_api_catalog — searchable manifest of ALL 554 public /api/* endpoints (the map) - zeq_http — call ANY of them through MCP with your Bearer key (the door) - 316 state-contract templates: GET https://zeqvm.com/api/contracts/templates - API EXPLORER (browse every endpoint in your browser): https://zeqvm.com/apps/api-explorer/ - Endpoint manifest as JSON: GET https://zeqvm.com/api/endpoints (filter ?q= ?method= ?auth=) ## NEW · HTTP QUERY (RFC 10008, June 2026) The safe, idempotent GET-with-a-body is supported framework-wide — the JSON body is merged into query params per the RFC semantics. Complex data grabs with no URL-length limits: ``` curl -X QUERY https://zeqvm.com/api/chain/recent -H 'Content-Type: application/json' -d '{"limit":2}' ``` ## Discovery - https://zeqvm.com/openapi.json - https://zeqvm.com/.well-known/ai-plugin.json - https://zeqvm.com/llms.txt (this file) ## What you are looking at Zeq is a physics virtual machine served over HTTP. The solvers, the operator catalogue, and the 1.287 Hz clock are not prompt scaffolding — they are endpoints with deterministic outputs and HMAC-signed receipts. Call /api/zeq/prove and check for yourself. The deeper mathematics is explained from inside once you have spun up your own machine. Source: https://github.com/hulyasmath/zeqsdk Contact: info@hulyas.org