Technical Documentation
Unified API reference + integration guides for every model on we64.com. OpenAI + Anthropic-compatible endpoints — drop-in replacement for the official openai SDK. Works with Cursor, Claude Code, IntelliJ, N8N, Dify, MCP clients, and more.
Base URL & Authentication
All we64.com models use the same OpenAI-compatible endpoint.
https://api.we64.com/v1https://api.we64.com/v1/we64_sk_...deepseek-v4-pro, kimi-k3, glm-5-2). Custom model names are not supported — use the full slug from the model list. pip install openai from openai import OpenAI client = OpenAI( api_key="we64_sk_...", base_url="https://api.we64.com/v1"
) response = client.chat.completions.create( model="deepseek-v4-pro", messages=[ {"role": "user", "content": "Hello!"} ]
)
print(response.choices[0].message.content)npm install openai import OpenAI from "openai"; const openai = new OpenAI({ apiKey: "we64_sk_...", baseURL: "https://api.we64.com/v1",
}); async function main() { const completion = await openai.chat.completions.create({ model: "deepseek-v4-pro", messages: [{ role: "user", content: "Hello!" }], }); console.log(completion.choices[0].message);
} main();curl https://api.we64.com/v1/chat/completions \ -H "Content-Type: application/json" \ -H "Authorization: Bearer we64_sk_..." \ -d '{ "model": "deepseek-v4-pro", "messages": [{"role": "user", "content": "Hello!"}] }'MCP Endpoint
Use your models as tools in Claude Desktop, Cursor and any MCP client.
https://api.we64.com/v1/mcpAuthorization: Bearer we64_sk_.../v1/chat/completions · Bearer is enough — no OAuth.{ "mcpServers": { "we64-models": { "type": "http", "url": "https://api.we64.com/v1/mcp", "headers": { "Authorization": "Bearer we64_sk_your-api-key" } } }
}Plug we64.com into your tools
Step-by-step guides for popular AI tools, IDEs, and frameworks. All use the same OpenAI-compatible Base URL + API key.
CursorEnable custom OpenAI Base URL in Models settings · Pro account required
deepseek-v4-pro), click Add. Test the connection, save the settings, and confirm in the Chat session. Claude Code (Local CLI)Terminal AI programming assistant · Win/Mac/Linux · Anthropic-compatible
git --version. Then install Claude Code in PowerShell:irm https://claude.ai/install.ps1 | iexcurl -fsSL https://claude.ai/install.sh | bash
# Or via Homebrew:
brew install --cask claude-code
# Or via NPM (requires Node 18+):
npm install -g @anthropic-ai/claude-code
# Verify:
claude --versionC:\Users\Username\.claude\settings.json; Mac/Linux ~/.claude/settings.json. Replace ANTHROPIC_AUTH_TOKEN with your API token and set ANTHROPIC_BASE_URL to our domain:{ "env": { "ANTHROPIC_AUTH_TOKEN": "we64_sk_your-api-token", "ANTHROPIC_BASE_URL": "https://api.we64.com", "ANTHROPIC_MODEL": "deepseek-v4-pro", "API_TIMEOUT_MS": "3000000", "CLAUDE_CODE_MAX_OUTPUT_TOKENS": "200000" }
}claude to start. On first run, follow the prompts to select a theme, confirm safety guidelines, and trust the directory. IntelliJ IDEAInstall Claude Code GUI plugin · Add custom vendor via Vendor Management
Open CodeAdd custom provider · Fill URL / Key / full model name · Save
OpenclawOne-click deployment · Command-line wizard configuration · Win/Mac/Linux
iwr -useb https://clawd.org.cn/install.ps1 | iexopenclaw onboard in the command line to enter configuration (skip download steps). Fill in Key / Base URL / Model ID as prompted. N8NConfigure OpenAI-compatible provider in credentials · Call models in workflow nodes
DifyLocal Docker deployment · OpenAI-API-compatible model vendor configuration
https://ghfast.top/https://github.com/langgenius/dify/archive/refs/heads/main.zip.env.example to .env. Go to the dify/docker directory and start all services:docker compose up -dhttp://localhost/ in your browser to create an administrator account and log in. Click the account avatar → Settings → Model vendor. Select and install "OpenAI-API-compatible", click to add a model, fill in the API Key, API URL (domain + /v1), and save.Please Read: Data & Hosting Location
Important disclosure about where your API requests are processed.
Every model on we64.com runs on infrastructure and data centers located in China. Requests and the content you send to the API pass through servers there. We don't control or audit that infrastructure ourselves — we provide access to it.
This is fine for most everyday use — coding help, drafting, general chat, experimentation. But if you're working with highly confidential, regulated, or sensitive data (client data, health records, trade secrets, government or legal work), we'd honestly recommend using an official provider with data-residency guarantees in your own region instead.
- • Coding help + debugging
- • Drafting + general chat
- • Experimentation + prototyping
- • Non-sensitive data processing
- • Personal + internal team tools
- • Client / customer confidential data
- • Health records (HIPAA / similar)
- • Trade secrets + proprietary IP
- • Government / legal / regulated work
- • Anything with data-residency requirements
We're upfront about this: all infrastructure is hosted in China, and we don't control or audit it ourselves. For everyday tasks that's rarely an issue, but for confidential, regulated, or sensitive work, please consider an official provider with data-residency guarantees in your region instead.
Supported API features (all models)
Need help integrating?
Email us for technical support — we reply within hours during business hours. Or chat with us on WhatsApp for instant help.