One key. One base URL. Your panel keeps your brand — we supply the models.
Crypto top-ups · USDT (BEP-20) · no KYC
To your panel, HELIOROUTE is no different from any other upstream. Three steps and you are live.
Create an account and top up with crypto. One key is all you need — it becomes your upstream channel.
Open your panel, add a channel of type OpenAI (and Anthropic if you serve Claude clients), and paste the key with our base URL.
Nothing changes on their side — same panel, same brand, same keys you issue. Model calls just flow through HELIOROUTE.
Everything your panel needs, on one host and one key. Point your channels at https://api.helioroute.com.
| Method | Path | What it’s for |
|---|---|---|
| GET | /v1/models | List every model available on the key — 69 models, in the standard OpenAI list shape. |
| POST | /v1/chat/completions | Chat completions — streaming (SSE) and tool / function calling. |
| POST | /v1/messages | Anthropic Messages shape (id, type, role, model, content, usage) — same key, same host. |
| POST | /v1/embeddings | text-embedding-3-small (1536 dims) and text-embedding-3-large (3072 dims). |
| ANY | Authorization / x-api-key | Both header styles work on both surfaces — send a Bearer token or an x-api-key. |
Both formats share the same base host — only the path differs. Send Authorization: Bearer <key> or x-api-key: <key>.
If it speaks the OpenAI or Anthropic format, it works. Pick your panel for the exact steps.
New API
Channel → OpenAI / Anthropic
one-api
Channel → OpenAI / Anthropic
sub2api
Upstream → OpenAI-compatible
Veloera
one-api fork
done-hub
one-api fork
Custom / code
Any OpenAI-compatible client
In New API an upstream is just a Channel. Add one OpenAI channel for the OpenAI surface and, if your customers use Claude clients, a second channel with type Anthropic — both carry the same HELIOROUTE key.
New API appends the path itself (https://api.helioroute.com/v1/chat/completions). If your build double-appends, keep the base at https://api.helioroute.com; if it needs the full base, use https://api.helioroute.com/v1.
Before you call it done
Panels differ in what they append. If the channel test fails, flip the base URL between https://api.helioroute.com and https://api.helioroute.com/v1 — one of the two is what your build wants. Then confirm the key directly:
curl https://api.helioroute.com/v1/models -H "Authorization: Bearer <key>"A healthy key returns 69 models. If that works but the panel test does not, the base URL is the culprit — not the key.
Built for the people running the panel — not just the people calling the API.
Chat, reasoning, coding, vision, image, audio and embeddings — the whole catalog behind a single upstream key. No per-model upstreams to babysit.
OpenAI (/v1/chat/completions) and Anthropic (/v1/messages) are served from the same host. Point an OpenAI-type channel, an Anthropic-type channel, or both at the same key.
A single HELIOROUTE key can be configured for 5000+ requests per minute, so a panel fanning many customer keys out through one upstream does not hit our ceiling first.
Top up with USDT on Binance Smart Chain (BEP-20). No cards, no invoices, no identity documents — credit lands automatically after on-chain confirmation.
Stays with you. HELIOROUTE only issues keys and serves model calls — your users, your dashboard, your logs and your brand all remain on your side. For billing we record request metadata only (model, token counts, cost, status), never your customers’ accounts or prompt content in the panel.
GET /v1/models returns the current list in the standard OpenAI shape — 69 endpoints today: 67 chat / reasoning / vision / image / audio models plus 2 embedding models. Most panels have a “Fetch models” button; if yours does not, paste the list yourself. The list grows as new models are verified, and your existing keys simply gain access — nothing to re-issue.
Per-key RPM can be set up to 5000+ for panel fan-out. Tell us the number you need when you request the upstream key and we will set it on yours. Individual customer keys you issue inside your own panel stay under your control.
Prepaid, per token, deducted from your balance in real time — the same balance your key draws on. Top up whenever you like with crypto; the bonus scales with the size of the top-up. See the pricing page for the current plans.
Yes. Your customers talk to your panel, on your domain, with the keys you issue — they never touch HELIOROUTE. Our key sits upstream and is invisible to them, so your brand stays entirely in front.
Model calls through the HELIOROUTE channel would fail, while the rest of your panel — accounts, billing, your own channels — keeps running. If you configure a second upstream as fallback, your panel can shift traffic there. We do not advertise a formal uptime SLA, and we would rather say that plainly than promise a number we cannot back.
Grab an upstream key, add one channel, and your existing panel serves the whole catalog — under your brand.
Questions? support@helioroute.com