Loading...

Docs · Getting started

Create an API key and choose a route

The key drawer step by step, what each route means, and the three 403 refusals a key can hit.

Open API keys in the sidebar and click Create API key.

The form

  1. Name: any label; the placeholder suggests production-backend.
  2. Group: the route the key is billed on. Nothing is preselected; saving without one fails with Choose a group. An N models button on each row expands its price table (USD per 1M tokens, USD per image or USD per second), with a Long context row where that tier exists.
  3. Quota: Unlimited quota on, or off with a Quota (USD) after which the key stops.
  4. Expiry: an Expiration time, or a preset: Never, 1 Hour, 1 Day, 1 Month.
  5. Quantity (creating only): up to 50 keys; the first keeps the name you typed, the rest get a random suffix.
  6. Advanced settings, collapsed by default: Model limits and IP Whitelist (supports CIDR), both empty.

Click Save changes. The key starts with sk-.

The routes

Auto route is listed first and covers the whole catalogue with one key. Each request goes to the lowest-priced line that can serve its model right now, normally the shared pool; when the pool cannot, it goes to the official line at its higher price, so the billed route can differ per request. The usage log shows that route under Group.

Claude, OpenAI and Grok official-line requests fall back to the shared pool when no dedicated line is configured; for a dedicated official-price line, write to support@topxea.com.

Three refusals

Three checks run before a provider is reached; each fails with HTTP 403:

IP Whitelist takes one IP or CIDR block per line; addresses can be spoofed, so pair it with a gateway such as nginx or a CDN.

Related

Previous: What TopxAI is · Next: Connect your SDK

Other languages: 简体中文