Skip to main content
As long as an app supports the OpenAI-compatible custom base_url + API key setting, you can switch it to OpenPAI in one step.

Common configuration

ItemValue
Base URLhttps://openp.ai/v1
API keysk-XXXXXXXXXXXXXXXX (from the console Tokens page)
ProtocolOpenAI / Anthropic / Google, your choice

Desktop GUI clients

Cherry Studio

Cross-platform multi-model chat client, recommended for getting started.

LobeChat

Open-source, self-hostable modern chat UI.

NextChat

Lightweight chat UI with one-click Vercel deployment.

ChatBox

Desktop ChatGPT client for Windows/Mac/Linux.

Coding assistants / IDEs

Cursor

AI-first code editor, supports a custom OpenAI base URL.

Cline / Continue

Open-source AI coding agents in VS Code.

Application frameworks

Dify

LLMOps platform, using OpenPAI as a model provider.

LangChain / LlamaIndex

Use the official OpenAI / Anthropic provider directly — just change base_url.

Official SDKs

OpenAI SDK

Python / Node / Go / Java

Anthropic SDK

Python / Node, using /v1/messages

google-genai

Python / JS, using the Gemini native protocol

Plain cURL

cURL cheatsheet

cURL templates for common tasks: chat, streaming, vision, tools, embeddings, images.

General tips

Manually enter the model ID shown in the OpenPAI console in the client’s model settings. Some clients hard-code OpenAI models in the dropdown — switch to custom model mode.
OpenPAI accepts requests both with and without /v1.
  • OpenAI SDK-style clients: https://openp.ai/v1
  • Anthropic / Google clients: https://openp.ai
OpenPAI enables CORS by default, allowing direct browser-side calls. But it is strongly discouraged to expose your API key in the frontend — forward through your own backend instead.