Reference

Runner API

The customer-facing contract for local repository registration and verified task dispatch.

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.

Runner workflow

The supported v1 workflow is:

  1. register a runner;
  2. register a trusted repository alias and base commit;
  3. preview a bounded task;
  4. submit it with a verification command and allowed paths;
  5. poll for its terminal result;
  6. inspect the patch, receipt, and settlement.

The runner uses the versioned /api/runner/v1/registrations, /repositories, and /tasks resources on your behalf. Use the packaged runner rather than scripting internal settlement endpoints; schemas may change during the invite-only beta.

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. Repository source remains in the local runner boundary.

Billing contract

Ormas charges only a successful, verified delivery:

  • input: $0.20 per million tokens;
  • output: $0.80 per million tokens.

A non-passing result or a delivery without usable metering incurs $0 Ormas service fee. Your model provider may still charge for attempts made with your local provider key. The $10 signup promotion pays Ormas service fees only and is applied before paid account balance.

Each completed task exposes receipt and settlement records so the token counts, fee, promotional debit, and paid-balance debit can be reconciled.

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.