A flat-rate LLM plan is cheaper than paying per token only above a break-even volume. For DeepSeek V4.1 Flash on BroadNet Inference, the $60 Full Moon plan breaks even at about 917 million input and 46 million output tokens a month with 80% cache hits. A full-time coding agent usually crosses that line. A side project or chat assistant usually does not.
Below are the formula, four worked monthly bills and the rival flat-rate plans, all from published prices. You can redo the math with your own numbers in the pricing calculator.
What are the two ways to pay?
Pay-as-you-go prices for DeepSeek V4.1 Flash, per 1 million tokens:
| Token type | Price per 1M |
|---|---|
| Input | $0.175 |
| Cached input | $0.0055 |
| Output (includes reasoning) | $0.52 |
The flat-rate plans cover the same model with no token meter:
| Plan | Price per session | Period |
|---|---|---|
| Full Moon | $60 | Month, renews |
| Orbit | $15 | Week |
| Meteor | $1 | Hour |
A session runs one request at a time. That is the only limit: no monthly token cap, no rolling window and no weekly quota. How sessions work.
How do you calculate the break-even point?
The math has three steps. You need your own token mix, not a list price.
- Find your blended price per 1M tokens. Add up a month of tokens by type and multiply each by its price:
cost = new input × $0.175 + cached input × $0.0055 + output × $0.52(all in millions of tokens). Divide by the total tokens. - Divide the plan price by that blend. The result is how many million tokens a month the plan replaces.
- Compare with your real volume. Above the line, the plan is cheaper. Below it, pay per token.
Here is the same math on one agent request, so you can see where the money goes. Say a coding agent sends a 50,000-token prompt, 40,000 of it read from cache, and gets 1,500 tokens back:
| Part | Tokens | Billed at |
|---|---|---|
| New input | 10,000 | $0.175 per 1M |
| Cached input | 40,000 | $0.0055 per 1M |
| Output and reasoning | 1,500 | $0.52 per 1M |
Multiply each row by its price and divide by 1,000,000. Then multiply by the number of requests a day. One request costs a fraction of a cent, but an agent that makes a few hundred calls a day turns that into a real monthly bill. The flat-rate vs per-token calculator does this for you.
Which workloads are cheaper on a flat plan?
These examples use the published prices above. The cache share is the fraction of input tokens read from cache, which is high for agents that resend the same files and system prompt on every turn.
| Workload | Input / month | Cache hits | Output / month | Pay per token | Cheaper option |
|---|---|---|---|---|---|
| Side project | 100M | 50% | 10M | $14.23 | pay as you go |
| Daily assistant | 300M | 50% | 30M | $42.67 | pay as you go |
| Full-time coding agent | 1,000M | 80% | 50M | $65.40 | Full Moon |
| Always-on agent | 3,000M | 80% | 150M | $196.20 | Full Moon |
The difference against one Full Moon session ($60) is $45.77, $17.33, $5.40 and $136.20 a month respectively. The always-on agent is the clear case: the plan bill stays the same however much the agent reads.
Where does the break-even line fall?
Coding agents read far more than they write. A typical shape is about 20 input tokens for every output token, with most of the input cached. At that mix, one million tokens cost a blended $0.06. The plan pays for itself at about 917 million input and 46 million output tokens a month.
One plan session also has a ceiling. At a typical speed of about 100 tokens per second, a session that generated non-stop for 30 days would produce about 259 million output tokens. Real agents spend much of their time reading, running tools and waiting, so the practical number is lower. If one agent is not enough, add sessions; see running parallel agents on a flat rate.
Flat rate or per token: side by side
| Pay per token | Flat-rate plan session | |
|---|---|---|
| Bill grows with | Every token, retry and long prompt | Number of sessions only |
| Best for | Light, spiky or experimental use | Steady agents that run for hours |
| Parallel requests | 4 in flight, 30 a minute per key | One per session; add sessions to add parallelism |
| Models | Every chat and speech model | DeepSeek V4.1 Flash only |
| Cache rate matters | Yes, a lot | No, for the bill |
| Smallest commitment | Nothing beyond your balance | One $1 Meteor hour |
There is also a third option. An hourly key for BroadNet Gemma 4 VL 26B costs $0.50 an hour, with one stream and 120 requests a minute. It suits short, heavy jobs on a small vision model rather than all-day agents; running one around the clock for 30 days would cost $360.00.
What moves the break-even point?
- Cache rate. Cached input costs $0.0055 per 1M instead of $0.175. A higher cache rate makes pay-per-token cheaper and moves the break-even point up. How to raise your cache rate.
- Reasoning. DeepSeek V4.1 Flash thinks before it answers, and those reasoning tokens are billed as output. Set
reasoning_efforttolowfor simple steps. Why reasoning can empty a reply. - Concurrency. A pay-as-you-go key allows 4 requests in flight and 30 a minute. A plan allows one request per session, but you can buy as many sessions as you run agents.
- Where you buy per-token access. DeepSeek’s own API also sells V4.1 Flash per token, with peak and off-peak rates. On 15 November 2026 its off-peak input prices (USD 0.15 per 1M, or USD 0.003 cached) were lower than BroadNet’s, and its output price (USD 0.60 off-peak, USD 1.20 peak) was higher at all hours, so the cheaper per-token option depends on your mix and time of day. Several other providers list the model below BroadNet’s per-token price too: see the DeepSeek V4.1 Flash price comparison across providers. If you stay on per-token billing, shop on price; the plan is what those providers don’t sell.
- Predictability. A per-token bill grows with every retry loop and every extra file. A flat bill does not, which is often worth something by itself for teams with a fixed budget.
Who else sells flat-rate LLM API access?
BroadNet is not the only flat-price option. These are the rival plans we could verify on each provider’s own pricing page on 15 November 2026. Prices are per month. Check the allowed-use terms as well as the price: one of them rules out agents.
| Provider and plan | Price | Concurrency | Models and context | What “flat” means |
|---|---|---|---|---|
| Featherless Chat | USD 25 | 4 concurrent units (“one 70B conversation, or four small ones at once”) | Any model in its catalogue, 32K context | “Unlimited tokens”, but only for “human-driven use”: the page rules out “app/API traffic”, “background automation” and coding agents |
| Awan LLM Core / Plus / Pro / Max | USD 5 / 10 / 20 / 80 | Not stated; Pro and Max list “parallel requests” | Small, medium and large model tiers; context not stated | “Unlimited tokens”, but capped at 20 to 200 requests a minute and, below Max, a daily request quota per model size |
| Standard Compute Starter / Economy / Standard / Pro | USD 19 / 39 / 89 / 249 | Starter: one agent at a time; Economy and up: parallel agents | Its full catalogue, routed per request | A monthly compute budget equal to the plan price; requests stop when it runs out |
| BroadNet Full Moon | $60 per session | One request per session; add sessions for more | DeepSeek V4.1 Flash only, 1,048,576-token context | No token meter, no daily or weekly cap |
Where they beat BroadNet. Awan LLM is far cheaper to start with, offers more models and lists parallel requests on its Pro and Max plans. Standard Compute routes to frontier models that BroadNet does not serve. Featherless Chat is cheaper and gives four concurrent units across a large catalogue, but only for chat you type yourself, so it does not fit an agent workload. If you need model choice or several parallel streams on one subscription, test Awan or Standard Compute first.
Where BroadNet differs. Its plan has no request-per-day quota (unlike Awan below Max) and no spend budget that runs out (unlike Standard Compute). It allows agents and API traffic, which Featherless Chat does not, and a far longer context than Featherless Chat’s 32K, which matters for coding agents that resend whole files. Whether a plan pays off still comes down to the break-even math above, so run your own numbers in the flat-rate vs per-token calculator.
What mistakes skew the comparison?
- Comparing against a chat subscription. A chat app plan is not an API key you can point your own tools at. Compare API prices with API plans. What “unlimited” really covers.
- Ignoring cached tokens. Pricing every input token at the full rate makes pay-per-token look far more expensive than it is.
- Measuring a quiet week. A week of holidays or a week of setup is not a normal month. Measure a week of real work.
- Forgetting parallelism. Three agents running at once need three sessions. Compare three plans with the per-token bill for all three.
- Forgetting the founders offer. With a founders code, Full Moon is $45 a month for the first three months, which lowers the break-even point for that period.
How do you measure your own usage before choosing?
- Run your real agent for a week on a pay-as-you-go key. New accounts start with $5 of credit.
- Turn on usage in streams with
stream_options: {"include_usage": true}and logprompt_tokens,prompt_tokens_details.cached_tokensandcompletion_tokens. The streaming guide shows how. - Multiply the week by about 4.3 and put the totals into the calculator.
- If the plan wins, buy a $1 Meteor hour and run the same loop on it before committing to a month.
Where BroadNet Inference fits
BroadNet sells both models of billing on one account, so you do not have to choose once and for all. Steady agents on DeepSeek V4.1 Flash fit a plan session. Other models, speech to text and occasional bursts stay on pay-as-you-go. If your volume sits well below the break-even line, the plan is the wrong choice, and the numbers above will show it. The calculator and this post use the same price file, pricing.json, last synced 2026-11-14.
