Introduction

How it works

Outcomes instead of turns. Get the change done.

The product

Outcomes instead of turns. Chat and a model router leave you watching tries. Ormas takes the next change in your project and the test that proves it — we can help write both — and runs it. You keep the hours for the rest of the work. The site does not merge or deploy your code. US-only. The 5% only when the task passes.

Create an account or sign in. Google, or an email magic link. After sign-in you land on Outcomes if it is enabled for your account, otherwise Account.

2 — Make an Ormas key

Open /app/keys. Create an Ormas key (tb_live_…). Copy it once. It is not a model-provider key.

On your machine:

ormas login

Paste the key. Point Claude Code, Codex, GrokBuild, or your own harness at https://api.ormas.ai. That is the Outcomes API. Do not paste provider keys into the portal.

3 — Send a spec

In a real repo, ask the harness for the next change and the test that proves it. Ormas can help write both. Work starts on your machine. This site shows the run after it happens.

4 — Read the receipt

A finished run has a receipt: what settled, the fee, and what you pay. Usage shows last 24h / 7d / 30d totals and a live log.

5 — Billing

Add a card in Billing when you want to run. Stop anytime. The console does not start work on its own.

A new account does not see Outcomes until the operator flags that user id. Empty list = no project yet, not a broken site.

Done when