Qwen models through one OpenAI-compatible API — coming soon
Qwen Turbo, Plus and Max through a single OpenAI-compatible endpoint — designed with prepaid credit, per-token metering, per-key limits and business billing built in.
Models
Qwen models served by Alibaba Cloud Model Studio, available through one endpoint at launch.
Qwen Turbo
Qwen Plus
Qwen Max
Start with one line
Already using the OpenAI SDK? Point base_url at the API host (available at launch) and keep your code.
from openai import OpenAI
client = OpenAI(
base_url="https://app.solver-one.ai/v1",
api_key="YOUR_API_KEY",
)
r = client.chat.completions.create(
model="qwen-plus",
messages=[{"role": "user", "content": "Say hello in Cantonese."}],
)
print(r.choices[0].message.content)Streaming, /v1/models and the usual OpenAI error shapes will be supported.
See the API preview.
How it will work at launch
Create an account
You will create an account and receive a metered API key.
Add credit
Prepaid credit by card (Stripe) at launch, or an invoice for business accounts.
Call the API
Point any OpenAI-compatible app at one endpoint and call Qwen models.
Metering & budgets
Every request will be metered per token against a prepaid balance. Per-key rate limits and a hard output cap will keep spend predictable.
Zero content retention
By design, prompts and responses pass through to the model provider and are never written to our database or logs; only token counts and cost are kept.
Enterprise-ready invoicing
Business accounts will be able to pay by Stripe-issued invoice with company details and tax IDs, numbered and archived — alongside receipts for card top-ups.
Built for teams that answer to finance and compliance
Solver-one is building one governed endpoint for Qwen models — with the billing, data-handling and controls a business needs to adopt it.
Governed access
Designed for multiple keys per account, each rate-limited; balances enforced; operator actions logged to an append-only audit trail.
Invoices & tax
Invoices with company name, address and tax ID, and receipts for card top-ups — both will be kept for 7 years.
Data handling
By design: no prompt or response content stored; API keys encrypted at rest; a documented sub-processor and data-residency policy at launch.
Compliance by country
Designed to capture the billing country at checkout, ask for cross-border transfer consent, and print per-country invoice footers.