What running an AI coding agent actually costs, per day

Updated 18 September 2026

Per-token API pricing is easy to find and hard to reason about. A rate card tells you the cost of one million tokens; it doesn't tell you what your actual coding-agent workload costs today, this week, or running unattended overnight. We pulled real per-token rates for Qwen3.8-27B, the model NeverMetered serves, across every provider hosting it, plus a couple of the cheapest alternative open models, and ran the numbers at realistic usage levels.

How we calculated this

We used four usage tiers, based on daily token volume and a cache-hit assumption that reflects how coding agents actually work (most of a request is the same file tree and conversation history sent again, which a well-cached provider bills at a steep discount): light (5M tokens/day, 90% cache hit, 3% of volume is output), moderate (15M, 90%/2.5%), heavy (30M, 93%/2%), and very heavy (50M, 95%/2%). Rates below are each provider's own published per-token price, checked directly against provider pricing pages and cross-referenced against a second aggregator; this is a snapshot from mid-September 2026 and these rates move, sometimes within the same month, so verify current pricing before budgeting a project around it.

The same open model, a dozen different prices

Qwen3.8-27B is open-weight, so nothing stops a dozen different companies from hosting it and setting their own price. They do, and the spread is bigger than you'd expect for literally identical model weights.

HostInput $/MOutput $/MModerate (15M/day)Heavy (30M/day)
DeepInfra$0.15$1.875$1.43$2.49
Chutes$0.24$2.20$1.51$2.49
Novita$0.42$3.00$2.90$5.05
Cerebras (fastest, ~1,500+ tok/s)$0.99$1.49$15.41$30.59

Cerebras is the outlier worth explaining rather than dismissing: its per-token price is high, but it's also reporting well over 1,000 tokens/second, dramatically faster than any of the other hosts here. That's a real, legitimate tradeoff (speed for money), not a bad deal, it just means "cheapest per token" and "cheapest for your actual workload" aren't always the same question, and neither is "fastest."

Cheaper open models exist, if the model choice is flexible

If you're optimizing purely for token cost and Qwen3.8-27B specifically isn't a requirement, a couple of other open models currently undercut it by a wide margin.

ModelInput $/MOutput $/MModerate (15M/day)Heavy (30M/day)
DeepSeek V4.1 Flash (off-peak)$0.15$0.60$0.49$0.76
GLM-5.3-Flash (list price)$0.15$0.50$0.49$0.87
DeepSeek's off-peak window is 01:00-04:00 and 06:00-10:00 UTC; peak-hour rates roughly double. GLM-5.3-Flash's price above is the list rate; a launch promo that ran through early September 2026 briefly cut it in half, so double-check whether a promotional rate is still live before you rely on it.

Where the math changes: running something all day

Everything above assumes a workday's worth of usage. The math looks different for an agent that runs continuously, overnight loops, background task queues, a single stream that never stops. NeverMetered's own measured throughput for Qwen3.8-27B is about 42 tokens/second on a single stream. Run that continuously for 24 hours and you're generating roughly 3.6 million output tokens a day, before counting the input side at all.

Daily cost at heavy usage (~30M tokens/day) for the same model across different hosts, plus two cheaper alternative models, at published per-token rates checked mid-September 2026.

Add in the input side, agentic coding resends a lot of context every turn, most of it cache-eligible, and a continuous single stream at a typical published Qwen3.8-27B rate lands somewhere around $8-12 a day, roughly $250-350 a month, for one stream that never stops. That's the exact case where a flat, priced-by-parallel-stream plan like NeverMetered's stops being a convenience and starts being the cheaper option outright, since the meter simply isn't running. See current plans for what a stream actually costs on a fixed monthly price instead of a running per-token bill.

Are these prices still accurate?
They're a snapshot from mid-September 2026, checked directly against provider pricing pages. Per-token API pricing changes often, sometimes with no announcement beyond an updated rate card, so treat this as a starting point and verify current pricing with the provider before committing budget to a specific one.
Why does the same model cost so differently across providers?
Different hosts run different hardware, different batching and caching setups, and different margins. Open weights mean anyone can serve the model, but nothing standardizes what they charge for serving it.
Is a cheaper alternative model actually worse than Qwen3.8-27B?
Not necessarily worse, just different. Independent benchmark trackers put some alternatives ahead of Qwen3.8-27B on general scores and behind on others; model choice should follow your actual task, not just the price column. Our own honest numbers for Qwen3.8-27B are on the model page.
What counts as a cache hit in this math?
Most providers charge a steep discount, often 75-90% off the input rate, when a request reuses a prefix (like the start of a conversation or a file already sent) that the provider still has cached from a recent request. Agentic coding tools that resend history every turn benefit heavily from this, which is why the cache-hit assumption matters as much as the headline per-token price.
Does NeverMetered charge per token at all?
No. Plans are priced by how many requests can generate at the same time (parallel streams), not by token volume. There's no token quota, 5-hour window or weekly cap on a paid plan; extra requests beyond your stream count wait briefly in a queue rather than costing more or failing. See current plans.
Sources