OEM / White-Label

White-Label AI Coding API

Wrap Claude and Codex in your own brand · your domain · self-service second-level keys · live in about 0.5–1 hour

#WhiteLabel#OEM#ClaudeCode#Codex#2026

White-Label vs Self-Build vs Direct SaaS

Enterprise buyers often ask: "what is the difference between going direct to Anthropic and wrapping it myself, versus white-label?" Going direct means building metering, caps, monitoring and cross-border networking yourself. White-label hands you that stack already running in production, and you own the branding and the selling. We do not represent Anthropic, OpenAI or Google, and we do not sublicense any rights from them — your agreement is with QCode. This section compares the cost, time and control of the two paths.

Capability Checklist

White-label ships with the following, all of it already in the partner console rather than on a roadmap:

01Brand customization: logo, domain (CNAME), color scheme, font, custom UI theme
02Second-level API keys: issue a separate key per customer, each with its own daily cap, total cap, concurrency limit and allowed host list
03Usage and billing: per-key consumption and balance in the console; your customers can check their own usage too
04Open API: /me, /balance, /usage, /keys to sync quota and usage into your own back office
05Three-language branded homepage: Chinese for Asia, English for the Americas, English plus Russian for Europe — toggled from the console after provisioning

Three Typical Use Cases

Software companies shipping AI features: add AI coding to an existing SaaS so it reads as "you shipped an upgrade", not "you bolted on a third party". Training providers and university labs: issue second-level keys in bulk, cap each one, reconcile in the console at end of term. SaaS upsell: package Claude and Codex capability as a premium SKU in your own product.

Technical Architecture: CNAME or Reverse Proxy

White-label runs on your domain via CNAME: point your domain at us, we handle DNS validation and TLS issuance, and the branded theme renders from your console settings. That configuration work is already covered by the 8% partnership fee on each top-up — there is no separate onboarding charge. You can also put your own backend in front and forward to us; that part is your implementation, and we only guarantee the API endpoint side.

Pricing and your margin

White-label has no separate price list — it follows your partner tier. The tier is set by a one-time top-up (A: CNY 20,000 → multiplier 0.75; B: CNY 10,000 → 0.80), with an 8% partnership fee on each top-up. Your cost of goods is simply top-up × 1.08 ÷ quota received: roughly CNY 0.32 per $1 of quota at tier A and CNY 0.35 at tier B. Your retail price is entirely yours, and your margin is the gap between it and that cost.

How onboarding works

① Use the calculator to work out what this top-up costs (amount + 8% partnership fee) → ② top up on the QCode recharge page → ③ send one application email with your brand domain, target region, intended tier, settlement currency and QCode account → ④ we configure the branded entry, DNS validation and TLS by hand, about 0.5–1 hour → ⑤ you receive your branded entry and first keys, set up branding and second-level keys in the console, and start selling. No KYC, no approval queue.

White-label vs building it yourself

Building it yourself means owning the upstream account pools, per-token metering and deduction, DNS validation and TLS issuance for your domain, cross-border networking and a customer-facing usage page. With white-label you top up, submit your domain, and about 0.5–1 hour later you have your branded entry and first keys. Entry tiers are A and B (one-time top-up of CNY 20,000 / 10,000).

Apply for white-label (tier A / B)

Your own branded domain · one key across three protocols · live in about 0.5–1 hour

Try first, then decide

Not sure which tier? Start with Starter ($8.57/mo) and upgrade when you're happy — the unused value of the old plan goes back to your balance.