API Endpoints

One base URL serves every region. Copy it into your client, then use the table below to see whether that client wants the full path or just the domain.

Base URL

🌐 Global smart routing

Requests are routed to the nearest healthy node in North America, Europe or Asia-Pacific automatically. There is no separate regional URL to pick.

https://jzstoken.com/api/v1

Which form does my client want?

OpenAI-compatible (Cursor, Cline, Cherry Studio, Chatbox, OpenCode, Hermes, SDKs)
https://jzstoken.com/api/v1
The client appends /chat/completions.
Codex (Responses API)
https://jzstoken.com/api/v1
Codex appends /responses.
Claude Code / Anthropic SDK
https://jzstoken.com
No /api/v1: these append /v1/messages themselves.
Clients that only take a domain
https://jzstoken.com
We also answer on /v1/*, so https://jzstoken.com/v1/… works.
💡 Never paste a full endpoint like /chat/completions or /messages into a Base URL field unless the client has a separate "Full URL" switch for it.

Endpoints we serve

POST /chat/completions
OpenAI Chat Completions
Most chat and coding clients.
POST /responses
OpenAI Responses
Codex and newer OpenAI SDKs.
POST /messages
Anthropic Messages
Claude Code, Anthropic SDKs, clients with an Anthropic mode.
POST /images/generations
OpenAI Images
Image generation.
POST /videos
Async video jobs
Video generation.
GET /models
OpenAI model list
Clients with a “Fetch models” button.

Quick connectivity test:

curl https://jzstoken.com/api/v1/models \
  -H "Authorization: Bearer YOUR_API_KEY"

Account and balance