How to Use Claude Code with Chonway API

Direct answer

If your Claude Code version supports Anthropic-compatible environment-based configuration, you can route calls through Chonway API by setting the Base URL to https://api.wos.one and providing a matching API key.

What this page is for

• Developers using Claude Code in local workflows.
• Teams standardizing one API entry point across multiple projects.
• Users who need a clear separation between CLI/API configuration and subscription-style products.

What to separate clearly

Claude API

This is the programmatic interface used by tools, scripts, and SDKs.

Claude Code

This is the developer tool layer. Whether it can use a third-party endpoint depends on client version, configuration behavior, and how the tool reads its environment.

Web subscriptions or account products

These should not be treated as the same thing as API keys or API balance.

Which endpoint format to use

For Claude Code, this page focuses on the Anthropic-compatible endpoint:

https://api.wos.one

Do not confuse it with the OpenAI-compatible endpoint used for other tools:

https://api.wos.one/v1

Minimal configuration

export ANTHROPIC_BASE_URL=https://api.wos.one
export ANTHROPIC_API_KEY=sk-your-api-key
claude

What to verify first

1. Your current Claude Code version supports the configuration method you intend to use.
2. The Base URL points to the Anthropic-compatible root endpoint, without /v1.
3. The API key belongs to the same service as the Base URL.

Common errors

401

Usually means the key is missing, malformed, copied incorrectly, or coming from the wrong service.

403

Usually means the request reached the service, but the key does not have access to the requested model or route.

Model not found

Check the model name against the current callable model list in the console.

Wrong Base URL

For the Anthropic-compatible setup here, the Base URL should be the root endpoint:

https://api.wos.one

Environment variables did not take effect

This often happens when the CLI is launched from a shell or IDE that did not inherit your updated environment.

The client is still reading old configuration

After updates or past experiments, the tool may still read older settings. Re-open the terminal and re-check the effective variables.

Risks and limitations

• Different Claude Code versions may not behave identically.
• A client upgrade can change configuration behavior, so validate again after updating.
• Third-party API routing should not be treated as proof that every Claude Code feature will always behave the same way.
• For sensitive or production-critical workflows, keep a fallback plan and review your operational dependency on any third-party platform.

Next steps

• For a broader explanation of Claude API access and interface choices, see How do I use the Claude API (via a proxy)?.
• For the main integration guide, see Integration Docs.
• For enterprise use cases and coordination, see Enterprise.

FAQ

Is Claude Code login the same as an API key?

No. Login state, subscriptions, and API credentials should be treated as separate systems.

Does this give access to every Claude feature forever?

No. Compatibility depends on the client version, supported routes, and the platform’s current capabilities.