Pricing
Qingzhong API is paid and billed from a wallet balance. Current model prices and group multipliers are listed on the pricing page and should be checked before sending requests, since rates and availability can change.
Learn moreOne base URL for OpenAI, Claude, Gemini and Grok, with keys, pricing and usage tracked.

Qingzhong API / 情种API is an analytics tool. Qingzhong API is a paid relay for developers that routes requests to OpenAI, Claude, Gemini and Grok style models through one base URL, while tracking API keys, wallet balance, pricing and per request usage in a single dashboard.
Qingzhong API (情种API) is a paid relay service that gives developers a single compatible endpoint for reaching multiple AI model families, including OpenAI, Claude, Gemini and Grok. Instead of integrating each provider's SDK separately, developers point their application at one base URL and route requests to a selected model, with request and response patterns following familiar formats such as /v1/responses and /v1/messages. The service is built for developers and small engineering teams who already work with AI APIs and want a managed layer for keys, billing and monitoring rather than a consumer facing AI assistant. Client configuration guidance is provided for tools such as Codex CLI, Claude Code and Cherry Studio, which suggests the typical user integrates the gateway into existing coding workflows or agent setups rather than building an integration from scratch. In practice, a new user creates an account, funds a wallet balance, and generates an API key that is separate from the account password. From there, the base URL (a primary address and a compatible backup address) is set in the client, a model is chosen from the live pricing page, and a test request is sent. Every call appears in usage records showing tokens, cost and timing, while the pricing page lists current rates and group multipliers so costs can be checked before committing. Public performance and quality pages add outside verification links for comparing models before picking a routing group. Qingzhong API positions itself as an independent relay rather than a one size fits all platform: it does not promise universal endpoint compatibility or a fixed service level, so developers are expected to confirm that a chosen model supports the endpoint they intend to call. This makes it a better fit for technically confident users comparing routing costs and model behavior across providers than for teams seeking a fully guaranteed, turnkey API management product.




Qingzhong API is paid and billed from a wallet balance. Current model prices and group multipliers are listed on the pricing page and should be checked before sending requests, since rates and availability can change.
Learn moreSupport is handled through a ticket center. Users are asked to include request IDs, model names and timestamps, and to remove API keys and personal information before sharing details.
Learn moreRequests are sent through a compatible base URL (primary and backup addresses) supporting formats like /v1/responses and /v1/messages, with client configuration guides covering tools such as Codex CLI, Claude Code and Cherry Studio.
Learn moreThe platform centralizes API key creation, wallet balance, live model pricing with group multipliers, per request usage records (tokens, cost, timing), and public performance and quality reports for comparing models before routing requests.





