Introduction
Getting started
Connect the GrokBuild-capable Ormas invite client to the control plane.
What the open beta does
Ormas authenticates coding tasks, runs a pinned GrokBuild worker, verifies the result, and returns a patch and receipt for your review. It does not automatically merge or deploy code.
GrokBuild is the open cockpit and worker runtime. Ormas curates models and inference paths — OpenRouter for day-one liquidity, plus Bittensor-aligned supply (SayGM, Engy, Chutes) when you add those keys — verifies work, and settles with receipts. No waitlist for US signup.
1 — Sign in (US)
Sign in with Google or an email magic link, then open Setup. New accounts receive $10 of Ormas service credit. This credit does not pay OpenRouter or another model provider.
2 — Keys: Ormas vs providers
Ormas key (control plane). Mint under Keys, then run ormas login and paste when prompted. In the product we call this an Ormas key. The secret string starts with tb_live_… — that prefix is the wire format for APIs and support, not the name you need to remember.
Provider keys (local only — never paste into ormas.ai):
| Key | Role |
|---|---|
OpenRouter (OPENROUTER_API_KEY) | Required for interactive beta launch today |
SayGM (SAYGM_API_KEY) | Recommended — Bittensor-aligned dual supply |
Engy (ENGY_API_KEY) | Recommended — Bittensor-aligned (e.g. glm-5.2) |
Chutes (CHUTES_API_KEY) | Recommended — Bittensor-aligned OSS / TEE path |
Store provider keys in the local client credential store or your shell env. A pure Bittensor-only path (no OpenRouter) is not the day-one golden path yet — keep OR, and add BT keys so Usage can show Bittensor-aligned share as routing expands.
3 — Install and check the early client
Use the pinned GrokBuild-capable Ormas client from Setup (early distribution while the public pin stabilizes). Then run:
ormas doctor
ormas grokbuild setup
Doctor is non-billable. grokbuild setup creates the private managed GrokBuild home without a provider call.
4 — Work interactively or headlessly
ormas grokbuild launch
Or run one verified worker:
ormas grokbuild run \
--cwd . \
--verify-command "python -m unittest -v" \
--max-attempts 2 \
"Implement the bounded task and keep tests green."
5 — Review before applying
Inspect the isolated patch, objective verification, and receipt. Incomplete cost is never treated as $0. Apply only after you accept the result. Refresh Usage on ormas.ai for activity and tier / Bittensor-aligned supply share.