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}"cfg="$(mktemp)"chmod 600 "$cfg"trap 'rm -f "$cfg"' EXIT{  printf 'url = "%s/models"\n' "${B3IQ_GATEWAY_BASE_URL%/}"} > "$cfg"curl --fail --silent --show-error --config "$cfg"

/v1/api/models has two views. Anonymous calls return the public network-wide catalog: models with at least one live, route-eligible profile on a public machine. Calls that send a valid customer-owned gateway key return only the models the machines on that account serve right now — the key's node scope is respected, any machine you've switched to Earn mode is excluded, and the account's model and route-tier policy still filters the result. The key-scoped list is served uncached, so it always reflects the current state of your machines.

Public Stats And Pricing

bash
curl --fail --silent --show-error "${B3IQ_GATEWAY_BASE_URL%/}/stats"curl --fail --silent --show-error "${B3IQ_GATEWAY_BASE_URL%/}/pricing"

These metadata endpoints do not require a gateway key and do not expose customer identity, prompts, outputs, raw tokens, node-local URLs, or private routes.

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