cheap/* · Pooled inferenceShared capacity, strict scrub, and the lowest-friction launch path for general traffic.
Estimated pooled usage
Cost-first
One API contract, three commercial lanes
Sell pooled, resale, and BYOK routes on one client contract.
OneKeyModels keeps the public surface OpenAI-compatible while you quote pooled cost, provider-backed resale, or customer-owned BYOK without changing the integration shape.
One OpenAI-compatible `/v1/*` contractRoute-aware billing basisUpgrade buyers without re-integrating
Public launch stays honest: one `/v1/*` contract, no provider-native endpoint promise, and pricing language tied to route, volume, and control.
Buyer snapshotChoose the lane by commercial posture, not by rewriting the client
OneKeyModels lets you quote cost-sensitive pooled traffic, provider-backed resale, and BYOK control inside the same external contract.
CostPooled access
Commercial moveUpgrade by route
ControlCustomer-owned BYOK
cheap/*Cost-first
resale/*Trust-first
byok/*Control-first
Route comparison
Show what changes commercially before the customer signs.
Each route keeps the same client contract, but the billing basis and sales posture are different. That difference should be visible on the public site.
resale/* · Official-provider resaleProvider-backed routing without pushing the customer into provider-native APIs or account setup.
Provider cost + margin
Trust-first
byok/* · Tenant-owned credentialsCustomer provider keys stay in the tenant boundary while the external API contract remains unchanged.
Customer provider usage
Control-first
Exact commercial terms should be quoted by route, volume, and support level. Do not collapse the three lanes into one public list price.
Built for
Different buyers should see themselves in a different lane.
Product teams
Ship quickly on one client contract
Start with pooled routes, then move production traffic up-market without a client rewrite.
Use this when the buyer wants one key, one API shape, and a clean path from testing to managed production traffic.
Lead with pooled cost, then introduce resale when trust or provider posture matters.
Resellers and agencies
Keep the sale in your contract, not the provider's
Offer a managed OpenAI-compatible surface while deciding route economics tenant by tenant.
Use resale when the buyer wants a cleaner trust story than pooled traffic but still expects you to own the relationship.
Quote managed routing and support, not just model cost.
Enterprise platforms
Keep customer keys inside the tenant boundary
Route regulated or high-control traffic through customer-owned credentials with the same `/v1/*` shape.
Use BYOK when the buyer cares more about ownership, credential isolation, and boundary clarity than lowest unit cost.
Sell boundary control and tenant isolation, not pooled savings.
Pricing language
Price by route behavior, not by hand-wavy platform slogans.
Use pricing language that matches the operational boundary the customer is buying: pooled savings, managed resale posture, or tenant-owned credentials.
Pooled launch pricingQuote this as the lowest-cost route for broad traffic and evaluation workloads.
Lower unit cost
Shared capacity
Managed resale pricingUse resale when the buyer wants provider-backed posture, cleaner trust language, or stronger support expectations.
Managed margin
Provider-backed
BYOK commercial modelBYOK should be sold as control and credential ownership, not as a cheaper substitute for pooled routing.
Boundary-first
Tenant-owned keys
Next step
Create the workspace, issue a key, and quote the lane that matches the sale.
The workspace keeps live model availability, keys, credits, usage, and tier posture in view so sales, ops, and support are reading the same contract.