Your machine, keys, connections, secrets and compute credits — all in one place, owner only.
Sign inPoint 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.
Two pools fuel your compute: free credits (1,287 on signup, 777 by daily claim — fuel only, never transferable) and paid ZEQ. Every compute mints a ZEQ envelope — the transferable token, worth more the better your compute’s precision. Paid-funded computes: 80% of the envelope is yours. Free-funded: the envelope backs the Foundation.
Everything that runs on your machine. Each console opens with this machine selected.