Your machine, keys, connections, secrets and compute credits — all in one place, owner only.
Sign inYour Vault is home base — but there's a whole ecosystem to build with. New here? Start at the Zeq Store, or get the editor & browser extensions.
Point an MCP client at the Zeq physics engine. Get your build key on the Overview tab, then paste this into your client config (e.g. claude_desktop_config.json) and restart.
Generate a machine key on the Overview tab, then any app that can make an HTTP request reads your machine's own secure context — authenticated by the machine key alone:
No key needed to try the engine — this returns a live, signed result you can verify:
Stop shipping .env files. Store your secrets and config once in ZSC — API keys, provider credentials, any env value — then any external app (local, server, CI, anywhere) fetches them at runtime with your machine key. Rotate without redeploying; every read is hash-linked; nothing secret ever lives in your repo.
Pull a secret from any app — authenticated by the machine key alone:
Your zero-knowledge, HITE-encrypted equation & password manager — AES-256-GCM, encrypted in your browser; the server only ever stores opaque ciphertext.
Free credits fuel your compute: 1,287 credits on signup, then a 128/day claim you can take only once you’re down to your last 5 (fuel only, never transferable), plus any paid credits. Every compute mints one ZEQ envelope — the transferable token, worth exactly the credits the compute cost (1:1, no split, no precision multiplier). Paid-funded → the whole envelope is yours, movable. Free-funded → the whole envelope backs the Foundation and you keep the soulbound light proof.
Human names for your machine, entangled with this ZID. Buy with compute credits or by burning an envelope — first come, first served. Resolution rides ZEQ Edge; no ICANN.
Lend your CPU to other people’s computations and be paid in envelopes. To take network jobs you bond 1,000 envelopes — and bonding is not a deposit: the envelopes stay in this vault, owned by you, the whole time. Bonding marks them immovable and records an attestation naming exactly which ones. There is no pool. Nothing is transferred to the Foundation.
You cannot contribute and experiment at once. Switching to contributing preempts your own running work — the two states cannot both be true, which is what stops a machine selling the same cycles twice.
If a result you return is proven wrong, the whole bond is withheld. “Proven” means the Foundation’s own independent re-execution disagrees with you and agrees with the challenger. If it matches neither, the job is marked not reproducible and nobody is slashed.
Everything that runs on your machine. Each console opens with this machine selected.