Same workload comparison
The same token mix is applied to each plan’s prices and model allowance. Check shared pools and time windows on the plan page.
Comparison example: 12,000 tokens/request · 83% cache read
Loading…
Anonymous user reports. They never change CP value; after 10 votes they count toward Today’s Pick. Press again to undo.
Example workload (12,000 tokens/request)
02Prices and allowances
Expand the ledger to verify four token prices, cost per request, model allowance and theoretical requests for this workload.
| Metric | OpenCode Zen Qwen3.5 Plus |
|---|---|
| Input / 1M | $0.20 |
| Cache read / 1M | $0.0200 |
| Output / 1M | $1.20 |
| Cache write / 1M | $0.25 |
| Cost / request Recalculated | $0.00160012,000 tokens/request |
| Model allowance Published | Pay as you goNo plan allowance; billed per request |
| Requests / month Recalculated | Pay as you goNo plan allowance; compare its rates instead |
| 5-hour limit Published | —Pay as you go |
| Weekly limit Published | —Pay as you go |
| Monthly limit Published | —Pay as you go |
03Official reference rows
Compare each provider’s reference token mix and published estimates below.
| Reference input / request | 1,000 |
|---|---|
| Reference cache read / request | 10,000 |
| Reference output / request | 1,000 |
| Reference cache write / request | 0 |
| Reference volume / request | 12,000 |
| Cost per request | $0.001600 |
| Model monthly allowance | Pay as you go |
| Capacity basis | No published reference profile; the site common workload is used instead |
Official source: OpenCode Zen · Snapshot captured: 2026-10-23