Authentication and API keys

Sign in, create and protect keys, and understand key limits.

Create and copy an API key

If key editing is unavailable, use an existing active key or contact support. Creating a key does not add account balance. The rolling 5-hour, 1-day and 7-day limits are spend limits in USD, not requests per minute.

  1. Sign in to the console with your account email and password. Complete the authenticator challenge if your account requires it.
  2. Open API Keys and choose Create API key. Give the key a name you will recognize in Usage.
  3. Choose an available group if you need a specific model route. Otherwise keep the default assignment.
  4. Set a USD quota and optional expiry or IP restrictions, then create the key. A blank or zero quota means unlimited key spend, subject to your account limits.
  5. Use Copy API key to copy the complete value. You can also reveal an existing key. Store it in a server-side environment variable.

API KeysPlaygroundUsage

Manage a key

  1. Use the usage bar to compare billed key spend with its quota. An unlimited key has no percentage bar.
  2. Open the three-dot menu for Edit, Enable or Disable, and Delete. Opening the menu does not change the key.
  3. Disable a key to stop future requests without deleting its record. Delete requires confirmation and stops that credential from working.
  4. Reveal or copy an existing key when needed. If it is exposed, replace it in your application and revoke the old key.

Set your key and choose a model

Replace the key placeholder with the complete key you copied. Choose an exact model ID available to that key; the public catalog is a reference and does not establish account access. These variables last for the current terminal session.

PowerShell

$env:KINETICROUTER_API_KEY = "YOUR_API_KEY"
$env:KINETICROUTER_MODEL = "YOUR_AVAILABLE_MODEL_ID"

macOS / Linux

export KINETICROUTER_API_KEY="YOUR_API_KEY"
export KINETICROUTER_MODEL="YOUR_AVAILABLE_MODEL_ID"

Troubleshooting

For support, include the time, model, request ID if supplied, and error status. Never send your API key, session cookie, or password. Error details vary by endpoint; use the returned status and message rather than assuming one universal error shape.

  1. Authentication failed: copy the complete key again, remove extra whitespace, and check its active status and expiry. Custom keys do not necessarily begin with sk-.
  2. Model unavailable or access denied: verify the selected key’s group and available model list. Check IP restrictions and provider route availability.
  3. Quota or balance exhausted: inspect the key’s quota and rolling USD limits, then the account balance or subscription usage. Changing a key quota does not fund the account.
  4. Request URL not found: use /v1 as the SDK base URL, and /v1/chat/completions for a direct Chat Completions request. Use the protocol supported by your chosen model.
  5. Rate-limited or temporarily unavailable: wait before trying again and check service status. Avoid repeatedly resending a request that may already have been processed.
  6. Stream stopped: keep the partial answer and check Usage. Start another request only when you want to retry.
  7. Playground with an IP-restricted key: the gateway sees the console server’s connection. A key that works from your application may not permit that connection. Keep the restriction unless you intend to change it.

kineticRouter Documentation