Introduction

How it works

Pay for outcomes, not for effort.

The product

Ormas pays for verified receipts, not inference turns. Describe the change and the test that proves it. Providers with public track records quote a firm price for the passing result. Pass → branch + receipt at the quoted price. Fail → you pay nothing.

Ormas is an Outcomes API for coding work, and Bittensor subnet 76. This site is the receipt: it shows the run after it happens and never merges or deploys your code. US-only.

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 your agent for the next change and the test that proves it; it prepares the task and posts it. Providers quote; you accept.

4 — Read the receipt

A finished run has a receipt: the test, the commit, the provider, and the price you paid — equal to the accepted quote. Usage shows last 24h / 7d / 30d totals and a live log.

5 — Billing

Add credits in Billing when you want to run. You are charged exactly the accepted quote; a miss costs nothing. The only Ormas fee is 5.5% when you buy credits, shown as its own line at checkout. 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