Calculate the token revenue from your idle GPUs
Estimated token revenue
per year · $1.2M a month
Kimi-K3 on 8×B300 nodes| How revenue grows | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| Token revenue | $15M | $19M | $25M |
Show the math
Calculation
- Nodes512 GPUs ÷ 8 per node64
- Idle node-hours a month64 × 730 h × 30% idle14,016
- Serving node-hours14,016 × 80% serving11,213
- Revenue per node-hour32 requests at once, measured$110
- Token revenue a month11,213 × revenue per node-hour$1.2M
- Token revenue a yeartoken revenue a month × 12$15M
Assumptions
- Our prices
- Kimi-K3: input $1.80, cached input $0.18, output $9.00 per M tokens.
- Serving load
- 32 requests at once on one 8-GPU node: 79,778 input and 565 output tokens per second, 91% of input from cache, 42.5 ms per output token. Earns $110 per node-hour. This is the measured point with the highest throughput that keeps latency under 50 ms per output token and under 2 seconds to the first token.
- Measured by
- SemiAnalysis InferenceX's agentic-trace benchmark of Kimi-K3 on one 8×B300 node, read 2026-10-28. About the AgentX traces
- Traffic
- Real multi-turn coding-agent sessions from InferenceX's AgentX traces, about 125,400 input and 890 output tokens per request with 91% of input served from cache, so output is under 1% of tokens. Shorter contexts or longer answers earn less per node-hour at our prices, because an output token takes far longer to produce than a cached input token.