---
title: "Claude and GPT Tool Integration Guide"
description: "API configuration guides and support scope for Claude Code, Codex CLI, OpenCode, OpenClaw, WorkBuddy, Hermes Agent, Cursor, Cline, Cherry Studio, and CC Switch."
headingIds: {"Programming Tools":"section-1","Desktop Assistants":"section-2","More Clients and Import Methods":"section-3","Agent Platforms":"section-4","Configuration Management":"section-5","Other Tools Supporting Custom APIs":"section-6","How to Confirm the Configuration Succeeded":"section-7"}
---

<aside className="docs-publication" data-pagefind-ignore>

Documentation maintained by [1ZheAI](https://1zheai.com/en/editorial/#publisher). [Sources and corrections](https://1zheai.com/en/editorial/).

Found an error? [Contact support](mailto:support@1zheai.com) with the page address and a description. Do not send API keys or account credentials.

</aside>
Enter the guide for the tool you are using. The statuses below are compiled from existing integration documentation and do not mean that all tool versions have been verified end-to-end. After a tool upgrade, please re-run the call verification on the page.

## Programming Tools

<CardGroup cols={2}>
 <Card title="Claude Code" href="/en/docs/quickstart-claude-code/">Native Anthropic integration. Environment variables, configuration files, and common issues. </Card>
 <Card title="Codex CLI" href="/en/docs/quickstart-codex/">Calling OpenAI / GPT models via the Responses API. </Card>
 <Card title="OpenCode" href="/en/docs/quickstart-opencode/">Distinguishing v1 and v2 configuration, custom OpenAI-compatible providers. </Card>
 <Card title="Cursor · usage limits apply" href="/en/docs/quickstart-cursor/">OpenAI-compatible integration. First check the scope of custom keys and interface differences. </Card>
 <Card title="Cline" href="/en/docs/quickstart-cline/">Anthropic mode is preferred; an OpenAI Compatible configuration is also provided. </Card>
</CardGroup>

## Desktop Assistants

<CardGroup cols={2}>
 <Card title="Cherry Studio" href="/en/docs/quickstart-cherry-studio/">Adding a custom provider in a chat client. </Card>
 <Card title="WorkBuddy" href="/en/docs/quickstart-workbuddy/">Adding a custom address via model settings; note the full URL and protocol toggle. </Card>
</CardGroup>

## More Clients and Import Methods

<CardGroup cols={2}>
 <Card title="Chatbox · one-click import" href="/en/docs/quickstart-chatbox/">Importing via link or clipboard JSON, with manual fallback configuration supported. </Card>
 <Card title="RikkaHub · QR-code import" href="/en/docs/quickstart-rikkahub/">Android provider QR code; key content is hidden by default. </Card>
 <Card title="ChatWise" href="/en/docs/quickstart-chatwise/">Custom provider fields and model configuration. </Card>
 <Card title="LibreChat" href="/en/docs/quickstart-librechat/">Admin YAML endpoint and per-user independent keys. </Card>
 <Card title="CC Provider" href="/en/docs/quickstart-cc-provider/">Anthropic configuration for the VS Code extension. </Card>
</CardGroup>

One-click protocols are only for operations that the client has publicly supported. ChatWise's open-conversation protocol is not the same as importing a key; LibreChat requires admin configuration. Do not treat all tools as having the same import link.

## Agent Platforms

<CardGroup cols={2}>
 <Card title="OpenClaw" href="/en/docs/quickstart-openclaw/">Configuring a custom Anthropic provider and default Agent model. </Card>
 <Card title="Hermes Agent" href="/en/docs/quickstart-hermes/">Configuring Chat Completions via the model wizard or a named provider. </Card>
</CardGroup>

<Note>The guides for OpenCode, OpenClaw, WorkBuddy, and Hermes Agent have been checked against official configuration, but end-to-end verification on this site is not yet complete. Please check the actual version against the guide and verify the call. </Note>

## Configuration Management

<Card title="CC Switch" href="/en/docs/quickstart-cc-switch/">Managing provider configuration for Claude Code to reduce manual switching. </Card>

## Other Tools Supporting Custom APIs

First check whether the tool can set an API address, key, and model ID, then choose a configuration based on the protocol:

| Protocol supported by the tool | This site's endpoint | Next step |
| --- | --- | --- |
| Anthropic Messages | `/v1/messages` | Check whether the client automatically appends `/v1`; see [address notes ](/en/docs/base-url/) |
| OpenAI Chat Completions | `/v1/chat/completions` | Usually fill Base URL with `https://1zheai.com/v1`; except for full endpoint fields |
| OpenAI Responses | `/v1/responses` | Fill Base URL with `https://1zheai.com/v1`; see [Codex CLI ](/en/docs/quickstart-codex/) |
| Only supports official account login | Do not use this site's API key | Check whether the tool has a separate custom provider setting |

## How to Confirm the Configuration Succeeded

1. Select the protocol and Base URL according to the guide; whether each tool needs `/v1` is shown in the [address comparison table ](/en/docs/base-url/).
2. Select a currently available model from [supported models ](/en/docs/models/).
3. Send one short request and check that the tool returns normally.
4. Verify the corresponding call in [call logs ](/en/docs/usage-logs/); do not judge which provider the request went through based only on the reply content.

If you encounter a problem, first see [error codes and troubleshooting ](/en/docs/troubleshooting/). If you are writing your own program, go to the [developer guide ](/en/docs/guides/).