Yes. All text models use the OpenAI wire format for /v1/chat/completions and /v1/responses, including streaming, tool calls and image content blocks. Anthropic Messages and Gemini-style paths are also terminated natively.
Change base_url to this endpoint and swap the API key. Nothing else in your request or response handling needs to change.
Per-token models are billed on input and output tokens separately, with output typically a multiple of input. Image models are billed per request. Every model page lists both the per-million-token rate and the multiplier, and the pricing table shows the full catalogue side by side.
Yes — repeated prompt prefixes are billed at a discount, because the upstream keeps the corresponding KV cache and does not need to re-run prefill. The platform routes requests so that a continuing conversation stays on the same upstream, which is what makes the discount actually apply. Put stable content (system prompts, reference documents) first and volatile content last.
Models are served through multiple independent upstream routes. Requests that hit a failing route are retried on another one, and channels are automatically taken out of rotation when their error rate crosses a threshold, then brought back when they recover.
Yes. For text-only models the gateway reads the image and injects a description into the prompt, so the same request body works across the catalogue. Native multimodal models receive the original image unchanged.
Alipay and WeChat Pay, with balance credited automatically after payment. Accounts are denominated in CNY; the pricing pages also show a USD equivalent for reference.
No. There is no free quota to farm, which is also why the platform does not need aggressive rate limiting on paid traffic. The low-cost model tier is inexpensive enough to evaluate on real traffic.
Use the key query page: paste your API key and it returns balance and usage from a read-only, masked view, on a rate limit separate from the main API path.
Yes. A one-click import script for Windows and macOS writes the model list into the local config of supported AI coding clients, so you do not have to type model ids by hand. The script runs once and exits — it registers no background task.
Ids follow the upstream naming and are kept stable. Version-suffixed variants (for example a dated build) are listed as separate ids so that a rolling upstream update cannot change behaviour under you.
Streaming is supported on all text models. Maximum output length is a property of each model and is listed per model; reasoning models count thinking tokens toward that budget.
Native means the upstream model itself accepts images and reads them directly — best for detail-sensitive tasks. Bridged means the platform performs the image understanding and passes text downstream — best when you want one cheap model to handle everything.
Yes — a single key works across the whole catalogue, and quotas or model scope can be restricted per key when you need to hand out narrower access.