Migration with an explicit compatibility boundary
Designed for teams that use OpenAI SDKs and need the documented Chat Completions subset.
Unsupported request fields return an explicit error instead of being silently ignored.
- Verified Chat Completions endpoint
- Secure API Key authentication and management
- Transparent input and output token pricing
- Real-time usage tracking and audit logs
Enterprise Access Control & Budget Protection
Protect your application budget by setting strict RPM, TPM, and concurrency limits alongside daily/monthly expenditure ceilings per project or key.
International Payment Support Roadmap
Recharge methods via Alipay and USDT are planned for future phases. Currently, the payment collection module is not enabled.
from openai import OpenAI
client = OpenAI(
api_key="qh_live_...",
base_url="http://localhost:4000/v1",
)
response = client.chat.completions.create(
model="qwen3.7-plus",
messages=[{"role": "user", "content": "Explain this error log."}],
)
print(response.choices[0].message.content)Common questions
Is the API compatible with the OpenAI SDK?
The public gateway follows the OpenAI-compatible chat completions pattern. Confirm model-specific features in the live catalog and documentation before production rollout.
Where do model availability and prices come from?
Public model pages read the active catalog exposed by the service. A model is not presented as available merely because its name appears in an article.
Are Alipay and USDT recharge active?
They are planned for the international version, but the collection module is not enabled in this phase. The site must not ask users to transfer funds until a real order and crediting workflow is available.
Can I limit spending by project or API key?
The existing product supports project and key controls, including budget and rate constraints. Exact fields and enforcement behavior are documented in the console and API documentation.