Bittensor multiprovider first. Patterns next.

Ormas is built for the Bittensor community first: stay in the open GrokBuild cockpit, run Grok, Opus 5, GLM, and Kimi across SayGM, Engy, Chutes, and OpenRouter, and see exact model × provider on Usage. Sticky model choice via /ormas-model — multiprovider preference when you only name the family; force provider when you want.

Honest claims only: we show realized Bittensor-aligned share from your traffic, not a fake “every request is a miner” story until proven.

GrokBuild is the open coding cockpit and worker runtime — the place you think, plan, and run agents. You are not trapped inside a single vendor's closed harness and model ladder.

Ormas is the control plane: auth, multiprovider model pick, verification, receipts, and prepaid settlement. Stay in GrokBuild; let Ormas make multiprovider work accountable.

Patterns (Deep Think, codebase review, backlog-prep) are multiprovider judgment loops — the product differentiator on top of verified leaves. Model-intelligence routing improves as measured outcomes accrue; it is not the first community wedge. Today the practical slate is Grok + Opus 5 + GLM + Kimi.

US open beta — sign in and start. No application waitlist. New accounts receive a $10 promotional service credit. The local GrokBuild client is still an early pin (Setup shows the exact install); that is early software, not artificial scarcity.

Provider keys stay on your machine. Task-relevant source may be sent to the model endpoint you use. Where OpenRouter is used, Ormas enforces Zero Data Retention (ZDR) and data-collection denial per request. Incomplete metering never settles as $0.