Troubleshooting
gw-link Error Reference and Troubleshooting Checklist
Almost every setup problem comes down to the key, the base URL path or the model name. Verify the key and network with /v1/models first, then match the error code below.
401 INVALID_API_KEY
The key is wrong, deleted or truncated, or your terminal still has an old environment variable. Re-copy the key and open a new terminal.
403 INSUFFICIENT_BALANCE / SUBSCRIPTION_NOT_FOUND
Top up if your balance is empty. If the key's group is subscription-only and you have no active subscription, subscribe or use a key on a balance group.
429 API_KEY_QUOTA_EXHAUSTED
The key's spending cap is used up — raise it in the console or use another key. Too many requests in a short time also return 429; retry later.
404 / wrong path
Claude Code and Gemini CLI base URLs must not include /v1; Codex and OpenAI SDK base URLs must.
Troubleshooting order
- Run curl https://gw-link.com/v1/models to check the key and network.
- Check the base URL matches your tool's rule (with or without /v1).
- Confirm the model ID appears in the /v1/models list.
- Check balance, subscription status and key caps in the console.
Configuration examples
Step 1: verify the key
A JSON model list means the key is valid; 401 is a key problem; timeouts mean a network problem — try https://gw-link.ai.
curl https://gw-link.com/v1/models \
-H "Authorization: Bearer sk-your-gw-link-key"FAQ
What usually causes a 401?
A wrong, deleted or truncated API key, or a tool reading an old environment variable. gw-link keys start with sk-.
It says the model doesn't exist — what now?
The model must be available to your key's group. Call /v1/models for the exact IDs and check the spelling in your tool.
What does a 503 mean?
The gateway or upstream is temporarily busy. It's transient — retry shortly, and contact support if it persists.
Claude Code returns 404?
Most likely ANTHROPIC_BASE_URL is https://gw-link.com/v1, producing /v1/v1/messages. Change it to https://gw-link.com.
Last updated: