First task

The website is the receipt. Work starts on your machine. Your client talks to the Outcomes API at https://api.ormas.ai — you do not call it by hand.

1 — Create an account

Go to ormas.ai/signup. Google (recommended) or an email magic link. US-only. No card required to look.

After sign-in you land on Outcomes if the operator has flagged your account, otherwise Account. A new account with an empty list is waiting to be flagged, not a broken site.

2 — Mint an Ormas key

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

3 — Log the client in

On your machine:

ormas login

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

4 — Post one real spec

In a real repo, ask the harness for the next change and the test that proves it. Ormas can help write the request and the test. A failing test you already have is fine too.

5 — Read the receipt

Refresh Usage. You should see the row in the log, plus 24h / 7d / 30d totals. Open the project under Outcomes for the receipt.

6 — Make it the daily driver

Integrate Ormas into your coding process or engineering graph. The first task is one spec. The product is sending the next change the same way every day.

Prepaid

Add a card in Billing when you want to run. Stop anytime.