How volume pricing actually works
Half-price frontier tokens sound like they should be impossible. Here is the mechanism — and, more usefully, here is why the discount differs per model and moves over time.
The mechanism
Model providers sell capacity in volume tiers. A buyer that commits to large aggregate throughput gets a materially better rate than one developer with a single API key. A gateway pools the demand of many developers, qualifies for the better tier, and passes part of the difference on.
Nothing about the model changes. You call claude-opus-5, you get Claude Opus 5. The only thing that differs is who is being billed and at what rate.
What you are taking on
| Risk | What it means | How to limit it |
|---|---|---|
| Uptime | You depend on the gateway's availability, not just the vendor's | Keep your direct key configured as a fallback |
| Model routing | You are trusting that the model you asked for is the model you get | Verify responses on a known benchmark before production |
| Continuity | Rates and availability can change | Do not prepay more than you would be comfortable losing |
| Compliance | Your data passes through a third party | Check the data retention policy if you handle regulated data |
Be realistic about this. These routes sit in a grey area relative to most vendors' terms of service. They are widely used and generally tolerated, but they are not an official reseller channel. If your workload needs contractual guarantees, a signed SLA or a compliance audit trail, buy direct.
How to switch safely
- Start with non-critical traffic and compare output quality on your own tasks.
- Keep the base URL in an environment variable so you can revert without a deploy.
- Monitor spend in both places for the first month.
- Do not move regulated or highly sensitive workloads through any third-party gateway.