Outcomes API

Control-plane URL

https://api.ormas.ai

The beta uses a local runner and Ormas MCP tools. It is not a drop-in Anthropic or OpenAI inference proxy.

Authentication

Use the Ormas key minted under Keys (wire format tb_live_…) to authenticate the client. Store it locally via ormas login. Your OpenRouter key (and optional SayGM / Engy / Chutes keys) are separate, stay local, and must never be sent as an Ormas header or portal setting.

Client workflow

The supported v1 workflow is:

1. your agent prepares the task (change, test, allowed paths, base commit);
2. post it;
3. accept a provider's firm quote (or set a ceiling and accept on arrival);
4. poll for the terminal result;
5. read the receipt and the result branch.

The wire names /api/runner/v1 and ormas-runner-v1 are internal identifiers and unchanged until the provider-identity release; they do not describe your role.

Data boundary

Task requests may contain the task brief, repository alias, base commit, verification command, allowed paths, budget, and safe runner metadata. They must not contain local filesystem paths, provider keys, environment dumps, or raw execution logs. Ormas never receives your source, diffs, prompts or credentials; a provider you accepted clones the repository under a per-job, single-repository credential.

Billing contract

You are charged the accepted quote. A miss is $0. Receipts are the authoritative record.

Idempotency and safety

Task submission and settlement use stable identities so retries do not create duplicate charges. Treat an ambiguous network result as retryable with the same identity. Never create a new task merely to poll an existing one.

Internal verification, key-resolution, and settlement routes are service-to-service interfaces and are not customer APIs.