Troubleshooting

Most TokenPool API setup issues come from one of five areas: sign-in state, API Key, base_url, local Codex configuration, or available quota. Check them in order before changing multiple settings at once.

Not signed in

Your personal API Key is only visible after sign-in. Click View my API Key on this page or open:

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

No API Key

Open the API Key page and create one. After creation, you can reveal, copy, test, or import it into CC Switch.

Wrong base_url

Recommended:

https://api.clawto.link

Standard:

https://api.tokenpool.dev

Do not use:

https://tokenpool.dev
https://tokenpool.dev/console

GPT-5.5 is missing in Codex

macOS / Linux:

TOKENPOOL_CODEX_MODEL='gpt-5.5' TOKENPOOL_CODEX_SET_DEFAULT_MODEL='1' bash -c "$(curl -fsSL 'https://cdn.tokenpool.dev/scripts/codex-fix-gpt55-catalog.sh')"

Windows PowerShell:

$env:TOKENPOOL_CODEX_MODEL='gpt-5.5'; $env:TOKENPOOL_CODEX_SET_DEFAULT_MODEL='1'; irm 'https://cdn.tokenpool.dev/scripts/codex-fix-gpt55-catalog.ps1' | iex

Connection failed

Check these in order:

1. The API Key was copied fully.
2. auth.json is valid JSON.
3. config.toml is in ~/.codex/config.toml.
4. base_url is https://api.clawto.link.
5. Your account has available quota.
6. Your network can reach the endpoint.

API Key leaked

Delete the old key immediately and create a new one. Do not wait for unusual usage to appear.

Related docs

• API Key
• base_url and Endpoint Choice
• OpenAI-compatible API
• Codex CLI

FAQ

Why does my Codex API key not work?

The most common causes are an incomplete API Key, the wrong base_url, invalid JSON in auth.json, missing quota, or a network issue reaching the endpoint.

Why does the endpoint fail?

Make sure you are using https://api.clawto.link or https://api.tokenpool.dev, not the website homepage or console URL.

Where can I see usage and quota?

Open the TokenPool console to check API keys, orders, delivery status, balance, and usage.