Skip to main content

Console Guide

Start from Getting Started​

Use Getting Started to confirm the request essentials before touching local config:

  • base_url: {{BASE_URL}}
  • API key format and copy action
  • Example request shape
  • Recommended model entry points

API Keys​

Use API Keys to create and manage keys for scripts, local tools, CI jobs, and coding agents.

  • Create one key per tool or workflow when possible
  • Rotate keys that have been shared or exposed
  • Delete keys that are no longer in use

model marketplace​

Use model marketplace to decide what to call.

  • Check the exact request name
  • Compare model type, context window, speed, and capability tags
  • Confirm whether the model matches your team plan scope

Playground​

If your role includes write access, use Playground before wiring a tool into real work.

  • Validate base_url, api_key, and model
  • Test messages and request parameters
  • Confirm the model returns the format you expect

Usage​

Use Usage to understand how your account is consuming quota.

  • Review total usage and recent traffic
  • Check which keys or models are driving spend
  • Confirm whether current workload still fits the plan

Logs​

Use Logs for request-level troubleshooting.

  • Inspect status code, latency, model name, and error details
  • Check whether the failing request reached the gateway
  • Match a local failure time with the corresponding request record

Teams​

Use Teams to confirm the team context attached to your account and keys.

  • Check which team you belong to
  • Confirm member roles and shared team settings
  • Review the team context when a key or model behaves differently than expected

Fast troubleshooting path​

  1. Confirm base_url in the tool is {{BASE_URL}}
  2. Confirm the key is active in API Keys
  3. Confirm the model name is copied from model marketplace
  4. Confirm the right team in Teams
  5. Retry in Playground if your role includes write access
  6. Open Logs and compare the error details