Same workload comparison

Start with what this workload buys you

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

Example workload (12,000 tokens/request)

Input
1,000
Cache read
10,000
Output
1,000
Cache write
0

02Prices and allowances

Keep prices, requests and plan windows in one evidence ledger

Expand the ledger to verify four token prices, cost per request, model allowance and theoretical requests for this workload.

Open prices, capacity and plan windows
Metric OpenCode Go Omen Alpha
Input / 1M$0.20
Cache read / 1M$0.0400
Output / 1M$0.66
Cache write / 1M$0.000000
Cost / request Recalculated $0.00126012,000 tokens/request
Model allowance Published $100Based on this model’s plan allowance
Requests / month Recalculated 79,365Estimated with the 12,000-token workload above
5-hour limit Published $12Plan window
Weekly limit Published $30Plan window
Monthly limit Published $60Plan window

03Official reference rows

The official reference behind each plan

Compare each provider’s reference token mix and published estimates below.

OpenCode Go View the provider’s reference workload Based on the published request estimate
Omen Alpha
Reference input / request300
Reference cache read / request40,000
Reference output / request100
Reference cache write / request0
Reference volume / request40,400
Cost per request$0.001726
Model monthly allowance$100
Published requests / month57,900
Published capacity / month2.3B
Capacity basisBased on the published request estimate
Calculation

Cost per request = add the four token classes after multiplying each by its price per 1,000,000 tokens.

floor($100 ÷ $0.001726) = 57,937

Official source: OpenCode Go · Snapshot captured: 2026-09-06