Hosted Gateway

The hosted gateway exposes OpenAI-compatible HTTP endpoints backed by B3IQ router policy. Inference is free: your keys route to the machines on your own account, the gateway enforces customer policy and quotas, and it records receipt metadata without storing raw prompts or outputs in the control plane.

Use https://b3iq.org/v1/api as the public gateway base URL for application traffic.

Endpoints

List models

bash
: "${B3IQ_GATEWAY_BASE_URL:?set B3IQ_GATEWAY_BASE_URL}": "${B3IQ_GATEWAY_KEY_FILE:?set B3IQ_GATEWAY_KEY_FILE}"cfg="$(mktemp)"chmod 600 "$cfg"trap 'rm -f "$cfg"' EXIT{  printf 'url = "%s/models"\n' "${B3IQ_GATEWAY_BASE_URL%/}"  printf 'header = "Authorization: Bearer %s"\n' "$(sed -n '1p' "$B3IQ_GATEWAY_KEY_FILE")"} > "$cfg"curl --fail --silent --show-error --config "$cfg"

/v1/api/models returns the models available to the authenticated account's machines. The key's node scope, account policy, machine mode, and current route health can narrow that list. Calls without an owner-scoped key return a valid OpenAI list with data: []; they do not expose another customer's models. The authenticated response is uncached. List models before calling chat and handle a route becoming unavailable between the two requests.

Public metadata and compatibility

/v1/api/stats returns public aggregate state. /v1/api/pricing is retained settlement-policy metadata for older integrations. It is not the price of a machine, a public GPU rental offer, or a per-token charge for your gateway key. Use the machine catalog for current configurations and commercial pricing. Inference through your own gateway key carries no per-request charge.

The /v1/models and /v1/chat/completions aliases have the same ownership boundary. SDK clients using those aliases set their base URL to https://b3iq.org/v1. /openrouter/models is retired; do not use it for customer discovery or infer available capacity from its existence in an old integration.

Chat completion

bash
: "${B3IQ_GATEWAY_BASE_URL:?set B3IQ_GATEWAY_BASE_URL}": "${B3IQ_GATEWAY_KEY_FILE:?set B3IQ_GATEWAY_KEY_FILE}"cfg="$(mktemp)"chmod 600 "$cfg"trap 'rm -f "$cfg"' EXIT{  printf 'url = "%s/chat/completions"\n' "${B3IQ_GATEWAY_BASE_URL%/}"  printf 'request = "POST"\n'  printf 'header = "Authorization: Bearer %s"\n' "$(sed -n '1p' "$B3IQ_GATEWAY_KEY_FILE")"  printf 'header = "Content-Type: application/json"\n'} > "$cfg"curl --fail --silent --show-error --config "$cfg" --data-binary @- <<'JSON'{  "model": "qwen3-8b",  "messages": [{ "role": "user", "content": "Say hello from B3IQ." }],  "max_tokens": 64}JSON

javascript
import { readFileSync } from "node:fs";const baseURL = process.env.B3IQ_GATEWAY_BASE_URL;const token = readFileSync(process.env.B3IQ_GATEWAY_KEY_FILE, "utf8").trim();const response = await fetch(`${baseURL}/chat/completions`, {  method: "POST",  headers: {    authorization: `Bearer ${token}`,    "content-type": "application/json"  },  body: JSON.stringify({    model: "qwen3-8b",    messages: [{ role: "user", content: "Say hello from B3IQ." }],    max_tokens: 64  })});console.log(await response.json());

Streaming

Set stream: true to request SSE streaming. Hosted streaming proxies the selected node stream while parsing final usage and b3iq.receipt_hash metadata for usage metering and receipt settlement.

json
{  "model": "qwen3-8b",  "messages": [{ "role": "user", "content": "Stream a short response." }],  "stream": true}

Routing and policy

A request passes three gates, in order, before it runs:

1. Key validity: the gateway key must be active, unexpired, and carry the required scope and a usable customer identity.
2. Rate limits and quota: per-key and per-account rate limits, and the account's daily token quota (default uncapped), are enforced next.
3. Own-account routing: the request dispatches only to a machine on your account that is online and serving the requested model. When none can serve it, the request fails closed with no_eligible_nodes.

Hosted chat can also fail closed when the model or route tier is outside your policy, or when an incident control pauses a route class, node, or payout path.

See Errors for stable machine codes, and Usage & Quotas for metering, rate limits, and the token quota.

Headers