FAQ

Account & Keys

How is a 211API key different from an official key?

A 211API key is created in the console, starts with sk-, and routes through the 211API relay. It is not an Anthropic / OpenAI / Google key and the two are not interchangeable. Always configure tools with the key created in the 211API console.

Can one key be shared across multiple tools?

Yes. The same API key can be configured into Claude Code, CodeX and Gemini CLI at once. 211API routes them uniformly and every call is tracked.

What if my key leaks?

Revoke it in the console immediately and create a new one. We recommend separate keys per environment, each with a quota cap.

Integration & Errors

401 auth failure

Confirm the environment variable holds a 211API console key, not a vendor official key. Then check the endpoint has no extra path suffix (Claude Code uses the root address; CodeX / Gemini CLI use the /v1 address).

Model not found

The model name in your config must exactly match the 211API console "Models" list — watch case and suffixes.

Connection timeout

Check the endpoint for extra path suffixes, and keep your terminal proxy settings consistent with your network environment.

Windows environment variables not applied

setx only takes effect in a new terminal. Inside PowerShell, read the variable back with $env:VAR_NAME to confirm.

Billing

How is billing calculated?

Actual token usage × model list price × channel multiplier. All multipliers are public, as low as 5% of official list price. See Pricing.

Where can I see usage?

The 211API console shows every call's routing, token usage and multiplier details in real time.

Get help

Hit auth, model or quota issues during integration? Submit a ticket in the 211API console — 24/7 monitoring, one-on-one human support, and our operations team responds promptly.