GPT88 / API Docs

Create and Manage GPT88 API Keys

Create, store, verify, and rotate GPT88 API keys, then confirm one request in usage records.

Know the three entry points

  • Console: sign in at agent.gpt88.cc.
  • Key management: open agent.gpt88.cc/keys after signing in.
  • API calls: use https://api.gpt88.cc as the standard API Base URL. Your console password is not an API key.

Create a traceable key

  1. Sign in to the GPT88 console and open API Keys.
  2. Select Create Key and use a name that identifies its purpose, such as web-prod, codex-dev, or team-reporting. Separate environments and applications so usage can be traced and keys can be revoked independently.
  3. Review the group, permission, and limit options shown by the current form. Confirm the model's group in the model catalog. Available options and account limits are defined by the live console.
  4. Copy and store the full key immediately after creation. The list is normally masked and cannot restore the full secret later.

Store and configure it safely

For local checks, pass the key through an environment variable. In production, use your deployment platform's secret manager.

environmentbash
# macOS / Linux
export GPT88_API_KEY="the full key copied when it was created"

# Windows PowerShell
$env:GPT88_API_KEY="the full key copied when it was created"
  • Read the key on your server. Browser bundles, mobile app packages, and public frontend variables cannot protect a long-lived secret.
  • Never commit it to Git. If a key was exposed, revoke it in the console and create a replacement; deleting the file alone does not invalidate the secret.
  • Use separate keys for development, test, production, and different applications to limit the impact of a leak or unexpected usage.

Verify a request

Use the GPT88 key and standard API Base URL in your application. Start with a minimal cURL or SDK request from Quickstart, then filter console usage records by time and key name to confirm the model, group, request status, and charge.

For unavailable models, check the model catalog and your account's available groups. A public listing alone does not prove that a model is enabled for your key.

Find, revoke, and rotate keys

The API Keys list supports searching by name or key and filtering by group and status. Review old test keys periodically. Before revoking an active key, find the services that still use it.

  1. Create and securely store a replacement key with a clear purpose name.
  2. Configure it in one service, send a minimal request, and confirm the usage record.
  3. Update the remaining services and check that each now uses the new key.
  4. Revoke the old key after it stops receiving requests. Revoke it immediately if it has been exposed.

For usage investigations, filter by API key, model, group, and time. Give support the time range, key name or final characters, model, and Request ID; never include the full key.

Troubleshoot common failures

  • 401 / invalid_api_key: check that you did not use your console password, that the key is complete, that the current process reads the environment variable, and that the key has not been revoked.
  • 403 / permission error: confirm the model, API, or group is available to the current key and account.
  • 429: check balance, rate limits, and current account limits. Creating more keys does not bypass account-level limits.
  • Terminal works, client fails: compare the client's Base URL, authentication method, and model field, then confirm that the client actually reads this key.

Follow the endpoint, authentication header, model, balance, and error-code checks in First Request Fails After Creating an API Key.

Migrate to GPT88

Treat credentials from another platform as credentials for that platform. Do not assume they work with GPT88 or that a website password is an API key. Create a new GPT88 key, then update your client's Base URL, key, and currently available GPT88 model ID.

Keep the old client configuration available during migration. After the new request succeeds and appears in usage records, revoke the old credential according to its provider's process. For GPT88 account entry points, see the GPT88 site migration guide.

Related guides