Crow API / v1

Inference without
the hyperscaler.

Run OpenAI-compatible requests on Crow capacity, pay one stable retail rate, and audit every terminal state.

01 / AUTHENTICATION

Bring an API key and funded escrow.

Send a Crow key in the bearer header. Before routing, the gateway validates the key, account policy, model availability and maximum estimated spend.

AUTHORIZATION HEADEROPENAI COMPATIBLE

Authorization: Bearer crow_live_••••

02 / CHAT COMPLETIONS

A familiar request shape.

POST /v1/chat/completions accepts standard messages, model, temperature, max tokens and stream fields. Crow returns standard completion objects and error envelopes.

POST /V1/CHAT/COMPLETIONSOPENAI COMPATIBLE

{
  "model": "crow-qwen3-8b",
  "messages": [{
    "role": "user",
    "content": "Explain the result."
  }],
  "stream": true
}

03 / STREAMING

Recover before the first token.

For streamed requests, Crow may retry before any output is emitted. After the first token, an execution failure closes the stream with a terminal error and a signed partial-usage receipt; streams are never spliced.

Reserved

→

Routed

→

Streaming

→

Receipted

04 / PROVIDER SETUP

Choose a model, prove the machine, then publish the price.

Connect any wallet on the provider page, select an approved model, and generate its single-use host command. The signed agent rejects unknown profiles and GPUs below the displayed VRAM requirement. Each offer is locked to the exact model and runtime that passed integrity, memory, throughput, latency, thermal and stability checks.

NVIDIA driver and supported CUDA runtime
Docker-compatible isolated execution
Stable outbound HTTPS/WSS access
Settlement wallet on Robinhood Chain

HOST AGENTOPENAI COMPATIBLE

$ sudo crow-provider configure crow-qwen3-8b
$ sudo crow-provider pair CROW-7Q4X-9N2M
$ sudo systemctl enable --now crow-provider

05 / RECEIPTS

Usage evidence, not request content.

A customer receipt binds the request identifier, Crow model, retail-price version, input and output counts, charge and terminal state to the Crow gateway signature. Internal execution evidence never appears in customer receipts.

request_idmodelretail_price_versioninput_tokensoutput_tokenscharged_microcreditsterminal_stategateway_signature

06 / PRIVACY MODEL

Know where the boundary actually is.

Provider transport is encrypted and workloads execute in isolated runtimes. Prompt bodies are not persisted by default. Operational metadata and signed receipts are retained for billing, disputes and abuse response.

ProtectedTLS transitRuntime isolationSigned meteringDefault no prompt retention

Not promisedGPU memory confidentialityProvider-blind executionRegulated-data complianceConfidential strategy safety

07 / ERROR SHAPES

Errors stay machine-readable.

The gateway returns an OpenAI-style error object with a stable Crow code. No usage is charged when a request fails before provider execution.

402 / INSUFFICIENT CREDITSOPENAI COMPATIBLE

{
  "error": {
    "message": "Compute credit balance is insufficient.",
    "type": "billing_error",
    "code": "insufficient_credits"
  }
}