Channels & Pricing

We offer 8 independent Channels, each with transparent pricing. When you create an API Key, you bind it to one Channel, and calls are billed at that Channel's rate.

Channel List

Channel	Billing Rate	Best For
Claude Official (Claude Code only)	1.4x	Dedicated to the Claude Code CLI, top-quality upstream, best stability; non-CC clients get a 503 rejection
Claude Official (any client)	2.0x	Cline / Cursor calling Claude / opencode / Open WebUI / Cherry Studio / custom SDKs calling Anthropic, any client supported
Claude AWS Bedrock 🆕	3.0x	AWS Bedrock upstream, high stability and high availability; all Claude models, ideal for production workflows with the strictest stability requirements
Budget Claude	0.5x	Any client, lowest price; budget tier, quality / stability relatively less reliable
Claude Sonnet Discount	0.5x ⭐	Primarily using Sonnet for coding / analysis — Sonnet series only
Codex	0.35x	OpenAI / Codex CLI / Cursor / Cline / Chatbox (supports both Responses + ChatCompletions protocols)
Codex Ultra-Budget 🆕	0.15x	All OpenAI-family models, lowest price; the only OpenAI Channel that supports image generation (gpt-image-2)
Gemini	0.5x	Long-form text, image understanding (Gemini 3 / 2.5, native protocol)

How the rate is calculated

Official price × Channel rate = your actual price. For example, Claude Sonnet 4.6 input at an official $3/M tokens:

• Claude Official (Claude Code only) 1.4x → $4.2/M
• Claude Official (any client) 2.0x → $6/M
• Budget Claude 0.5x → $1.5/M
• Claude Sonnet Discount 0.5x → $1.5/M

Combined with the Top-up rate of ¥1=$1, that equals ¥1.5/M.

How to choose among the four all-model Claude Channels

The models / context length are identical — the differences are client compatibility + upstream quality + rate:

• Claude Official (Claude Code only) 1.4x: top-quality upstream, best stability. But the channel only accepts the official Claude Code CLI (claude-cli/X.Y.Z UA + standard metadata). Cline / Cursor / opencode / Open WebUI / custom SDKs, etc. will get a 503.
• Claude Official (any client) 2.0x: a self-built account pool, usable by any client speaking the Anthropic protocol, with good stability.
• Claude AWS Bedrock 3.0x: AWS Bedrock upstream, for workflows with the most demanding stability / high availability requirements (production agents, long-running batch jobs, no tolerance for a single failure). Higher price, but the best perceived SLA.
• Budget Claude 0.5x`: any client, lowest price, but quality / stability relatively less reliable — suited for scenarios with high tolerance for occasional failures that prioritize value.

Only using the Claude Code CLI → 1.4x. Other tools needing stability → 2.0x. Production-critical workflows needing maximum stability → AWS Bedrock 3.0x. Chasing the lowest price and tolerating occasional failures → 0.5x budget tier.

How to choose between the two Codex (OpenAI) Channels

The supported models are exactly the same (GPT-5.x / Codex series) — the differences are rate + image generation:

• Codex 0.35x: a stable, established Channel for plain-text calls (Chat Completions + Responses). Does not support the gpt-image-* series.
• Codex Ultra-Budget 0.15x: a new upstream Channel with the lowest price. The only OpenAI Channel with image generation enabled — you can call gpt-image-2 directly to generate images.

No image generation needed + want stability → Codex 0.35x. Need image generation / want to save money → Codex Ultra-Budget 0.15x.

Models Supported by Each Channel

Below are the exact strings you must put in the request's model field. There is no short-name fallback — writing gpt-5 instead of gpt-5.4 will get you a 503 No available accounts.

Claude all-model channels (Claude Code only / any client / AWS Bedrock / Budget Claude)

claude-opus-4-8                  ← flagship (latest)
claude-opus-4-7
claude-sonnet-4-6                ← workhorse (recommended)
claude-haiku-4-5-20251001        ← cheap & fast
claude-opus-4-6                  ← prev-gen flagship
claude-opus-4-5-20251101         ← prev gen
claude-sonnet-4-5-20250929       ← prev gen
claude-fable-5                   ← new model (the two "Official" channels only)

# claude-fable-5 is available only on Claude Official (Claude Code only) + Claude Official (any client);
#   AWS Bedrock / Budget Claude do not include it yet. The other models are identical across the
#   four channels — the differences are client compatibility + upstream quality + rate (1.4x / 2.0x / 3.0x / 0.5x)

Claude Sonnet Discount

claude-sonnet-4-6                ← 主力（推荐）
claude-sonnet-4-5-20250929       ← 上代

# ⚠️ 仅支持 Sonnet 系列。调 opus / haiku 会拿到 503
#   "channel pricing restriction"

Codex (0.35x)

gpt-5.5                          ← 最新
gpt-5.5-codex                    ← Codex 编码专项（最新）
gpt-5.4                          ← 主力（推荐）
gpt-5.4-mini                     ← 便宜
gpt-5.3-codex                    ← 编码专项
gpt-5.3-codex-spark              ← Pro 专属(推理研究预览)
gpt-5.2 / gpt-5.2-pro

# 仅以上列表内的模型可用,**未列出的模型一律返 503**
# 图像生成(gpt-image-*) 不在该渠道 — 要生图请用 `Codex Ultra-low-cost` 渠道
# Pro 系列(gpt-5.5-pro / gpt-5.4-pro)是 Responses-API only,Codex 通道不可用

Codex Ultra-low-cost (0.15x)

gpt-5.5 / gpt-5.5-codex          ← 跟 Codex 渠道一致
gpt-5.4 / gpt-5.4-mini
gpt-5.3-codex / gpt-5.3-codex-spark
gpt-5.2 / gpt-5.2-pro
gpt-image-2                      ← 🎨 仅本渠道支持图像生成

# 支持模型 = Codex 渠道全部 + gpt-image-2
# 价位最低 (0.15x) + 唯一开了生图

Gemini

gemini-3.1-pro-preview           ← 旗舰（带 thinking）
gemini-3-pro-preview             ← 主力
gemini-3-flash-preview           ← 快速
gemini-2.5-pro                   ← 上代旗舰
gemini-2.5-flash                 ← 上代快速

The Gemini Channel uses the native protocol

Gemini uses Google's native /v1beta/models/{model}:generateContent (or :streamGenerateContent?alt=sse) endpoint, and does not use the OpenAI / Anthropic compatible interface. Each contents item in the request must explicitly include "role": "user", otherwise Google will return 400 Request contains an invalid argument. See FAQ for details.

🎨 Image generation is live (2026-05-22)

gpt-image-2 image generation is now supported via the Codex Ultra-Budget Channel.

Two ways to use it:

1. Call the API directly: POST /v1/images/generations, set model to gpt-image-2, requires an API Key bound to Codex Ultra-Budget
2. Built-in dashboard tool: after logging in, the sidebar entry "AI Image Generation" lets you pick a Key + prompt to generate, with support for reference-image editing + multiple platforms (OpenAI / Gemini / Antigravity)

The Gemini-series image models (gemini-3-pro-image / gemini-3.1-flash-image, etc.) are currently not open for client calls — to be evaluated later.

⚡ 1M Long Context (Beta)

3 models support a 1M-token context window (default 200K):

Model	Default	1M Mode
claude-opus-4-7	200K	✅
claude-opus-4-6	200K	✅
claude-sonnet-4-6	200K	✅

How to enable it

Add a header to the request:

anthropic-beta: context-1m-2025-08-07

If you have another beta enabled at the same time (e.g. thinking), just separate them with a comma:

anthropic-beta: context-1m-2025-08-07,interleaved-thinking-2025-05-14

When calling a model that supports 1M, the header is passed through to Anthropic and 1M mode takes effect. When calling a model that does not support 1M (haiku / older opus / older sonnet), we automatically strip this header on our side and won't send an abnormal request upstream — so even if you specify the wrong model, it won't trigger Anthropic's risk controls.

Cost reminder

A single 1M-context request consumes far more tokens than 200K mode. Anthropic officially charges 2x for 1M-context input:

• Normal mode: Sonnet 4.6 input $3/M
• 1M mode (the portion beyond 200K): Sonnet 4.6 input $6/M

Converted to our pricing:

• Claude Official (Claude Code only) 1.4x → 1M mode $8.4/M
• Claude Official (any client) 2.0x → 1M mode $12/M
• Budget Claude 0.5x → 1M mode $3/M
• Claude Sonnet Discount 0.5x → $3/M

A single call that fills the entire 1M context can cost on the order of $3–10, and multiple full-load calls within 5h will quickly consume your scheduling quota. We recommend:

• Only enable it when you truly need it (large codebase analysis, long document summarization)
• Turn it off when done
• Keep a buffer in your Top-up Balance

Which Channel Should I Choose

graph LR
    A[选择渠道] --> B{用什么工具?}
    B -->|Claude Code CLI| C{Sonnet 还是 Opus?}
    C -->|Sonnet| D[Claude Sonnet Discount]
    C -->|Opus / Haiku| E[Claude 官方<br/>仅限claude code 1.4x]
    B -->|Cline / Cursor 调 Claude / opencode / 调 Anthropic SDK| Q{要稳定还是要便宜?}
    Q -->|要稳定| F[Claude 官方<br/>不限客户端 2.0x]
    Q -->|生产关键 要最稳| K[Claude AWS Bedrock 3.0x]
    Q -->|要最低价| L[Budget Claude 0.5x<br/>质量不稳定]
    B -->|Codex CLI / Cursor / OpenAI 兼容| G{要生图吗?}
    G -->|要生图 或 想省钱| M[Codex Ultra-low-cost 0.15x<br/>支持 gpt-image-2]
    G -->|纯文本 要稳| N[Codex 0.35x]
    B -->|要多模态/长文档| H[Gemini]
    B -->|多渠道混用| I[创建多个 Key,<br/>各绑一个渠道]

Simplified Recommendations

• Claude Code CLI, primarily Sonnet → Claude Sonnet Discount (cheapest, Sonnet only)
• Claude Code CLI using Opus / Haiku → Claude Official (Claude Code only) 1.4x (top-quality upstream)
• Cline / Cursor calling Claude / opencode / Open WebUI over the Anthropic protocol, needing stability → Claude Official (any client) 2.0x
• Production-critical workflows needing maximum stability → Claude AWS Bedrock 3.0x
• Any client, chasing the lowest price, able to tolerate occasional failures → Budget Claude 0.5x
• Codex CLI / Cursor calling GPT in plain text → Codex 0.35x
• Need image generation / want maximum savings → Codex Ultra-Budget 0.15x
• Not sure → Codex Ultra-Budget (best compatibility, works with almost any tool that supports the "OpenAI API" + lowest price + image generation as a bonus)

Top-up Rate

¥1 = $1 (Top-up rate 1.0x). For example:

• Top up ¥100 → wallet Balance $100
• One full Claude Sonnet 4.6 conversation costs about $0.018 (including 1k input + 500 output tokens, 0.5x discount Group)
• That works out to roughly 5500 medium-length conversations per ¥100

See Top-up & Plans for details.

Service Rate Limiting

To keep the service stable over the long term, our scheduling system automatically controls the call volume per unit of time. When requests come in too densely within a short window, some requests will temporarily return 429 and automatically recover within 1–5 minutes.

If your workflow is sensitive to occasional 429s, we recommend:

• Implementing simple exponential-backoff retries in your client
• Spreading out usage (avoiding the 19:00–23:00 peak)
• Rotating across multiple Keys for important tasks

See FAQ for details.