Docs for buyers and operators

Compare the route first, then send the request.

These notes keep the launch contract simple while showing how `cheap/*`, `resale/*`, and `byok/*` should be sold, quoted, and described without inventing unsupported public pricing.

One `/v1/*` contractThree route behaviorsQuote by lane, not by rewrite
Create workspaceCompare route pricing
Public surfaceOne OpenAI-compatible `/v1/*` contract for launch-ready traffic.
/v1/* only
No native endpoints
Route selectionChoose the tier by model ID and keep the client integration stable.
cheap / resale / BYOK
Same client
Quote disciplineCommercial terms should follow route, volume, and support expectations.
Route-aware
No fake list price

Buyer comparison

How to position the three tiers

Make route choice legible before a prospect ever opens the dashboard.

cheap/* · Pooled inferenceCost-sensitive volume, testing, and broad usage. Use this when you want one API contract and the lowest-friction launch path.
Estimated pooled usage
Cost-first
resale/* · Official-provider resaleHigher-trust routing without provider-native lift. Use this when the buyer wants provider-backed posture without moving to provider-native APIs.
Provider cost + margin
Trust-first
byok/* · Tenant-owned credentialsControl boundaries, enterprise credentials, and ownership. Use this when the buyer wants their own provider keys and a clearer tenant boundary.
Customer provider usage
Control-first

Pricing language

Use pricing language that matches the lane

Keep the commercial story tied to route behavior instead of publishing unsupported exact rates.

Pooled commercial storyLead with lower operating cost, shared capacity, and strict scrub.
Cost-first
General traffic
Resale commercial storyQuote provider-backed posture and managed routing rather than a generic discount claim.
Trust-first
Managed production
BYOK commercial storySell credential ownership and tenant control, not pooled savings.
Control-first
Regulated workloads

Quickstart

First request

Start with a model ID that matches the intended execution lane. The client shape stays the same across tiers.

View live catalog
curl https://api.onekeymodels.com/v1/chat/completions \
  -H "Authorization: Bearer $ONEKEYMODELS_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "cheap/gpt-5.4",
    "messages": [{"role": "user", "content": "hello"}]
  }'

Commercial note

What not to promise

Avoid universal pricing statements, because the buyer should compare route, volume, and control instead.

Sign in
  • Do not claim one fixed price for every route.
  • Do not blur pooled cost, resale trust, and BYOK control into one headline.
  • Do not describe BYOK as a fallback for pooled execution.
  • Do not publish exact commercial terms unless they are actually approved.