Get and Use an API Key

An API Key is your credential for calling TokenPool's OpenAI-compatible API service. Codex App, Codex CLI, OpenCode, and other supported tools do not use your TokenPool password; they only need an API Key and a base_url.

Create or view an API Key

1. Open the TokenPool console.
2. Go to API Keys.
3. Create a key if you do not have one.
4. Reveal, copy, test, or configure an existing key.

https://tokenpool.dev/console/api-keys

Screenshot placeholder: API Key list in the console.

API Key and base_url

Most supported tools need two values:

For Codex workflows, use the key together with an OpenAI-compatible endpoint. The recommended endpoint is:

https://api.clawto.link

Where the key goes

Codex App / Codex CLI:

{
  "OPENAI_API_KEY": "<your TokenPool API Key>"
}

OpenCode:

{
  "provider": {
    "openai": {
      "options": {
        "apiKey": "<your TokenPool API Key>"
      }
    }
  }
}

Keep it private

• Do not share your API Key.
• Do not commit it to Git.
• Do not show it in public screenshots.
• Delete and recreate it if it may have leaked.

Rotate a leaked key

If a key may have leaked, do not wait for unusual usage to appear.

1. Delete the exposed key in the console.
2. Create a new API Key.
3. Update auth.json, OpenCode config, CC Switch, or any environment variable that used the old key.
4. Review usage and quota in the console.

FAQ

Is a TokenPool API Key the same as my password?

No. Your TokenPool password or login session is for the website and console. The API Key is only for API requests from supported tools.

Can I use this as a Codex API key?

Yes. Use the TokenPool API Key with the Codex App or Codex CLI configuration shown in the Codex docs.

Can I share one API Key across multiple machines?

You can, but separate keys are easier to rotate and audit. Create separate keys for different machines or workflows when possible.