claude plan vs api: compare the bill you will pay

the plan prices and api rates

as of 12 november 2026, anthropic's pricing page lists these individual plans. prices exclude tax.¹

the $200 plan is now called ultra, not max, so older comparisons may use the wrong name. anthropic also says pro, max and ultra include claude code alongside its web, desktop and mobile apps.¹²

as of the same date, the api pricing page lists sonnet 5.5 at $2 per million input tokens and $10 per million output tokens. opus 5.5 is $4 input and $20 output per million. input and output must be counted separately; multiplying all tokens by the cheaper input rate understates the bill.³

example calculations, not typical bills

these are invented workloads to show the arithmetic. they are not measured bot usage or promises about how much work fits a plan. amounts below cover the stated input and output only, before credits and any other charges.

• example, a small sonnet workload: 1 million input tokens and 0.1 million output tokens. (1 × $2) + (0.1 × $10) = $3. that's less than pro's $20, but a plan and the api aren't the same thing, so this doesn't tell you what pro would cover.¹³
• example, a larger sonnet workload: 8 million input and 2 million output tokens. (8 × $2) + (2 × $10) = $36. that exceeds $20 in raw api usage. it still does not prove this workload fits pro's limits.³
• example, the same token counts on opus: (8 × $4) + (2 × $20) = $72. changing the model changes the token subtotal even when counts stay the same.³

for your own calculation, use input millions times the input rate, plus output millions times the output rate. then check credits and the actual billing terms for your account. do not convert a monthly plan price into an invented number of included tokens.

included api credits change the comparison

as of 12 november 2026, the pricing page lists $100 in monthly api credits with max and $200 with ultra. anthropic's support article, updated 7 october 2026, says max, ultra and team now include monthly api credits, and that signed-in agent sdk and claude -p still draw from plan limits.⁴

keep these quantities separate in your notes: the plan payment, included credits, raw api charges and anything due beyond credits. do not add the full raw api subtotal to a plan payment if your provider has applied credits to it. equally, do not assume all possible charges are covered simply because a monthly credit exists. check your provider's current billing details.

for someone already paying for max, the useful question may be whether existing credits cover the proposed work. for someone buying a plan only for one task, the whole plan price matters.

the login route is a terms question too

as of 12 november 2026, anthropic describes sign-in to the unmodified claude code binary while restricting developer credential handling and reserving usage-credit billing for certain third-party tools; none of this says whether a particular app is covered, so check your provider's current terms and the sign-in overview.⁵⁶ if two answers online disagree, the dated sign-in log shows which rule came first.

add the computer only if you need one

dusk's ai usage is billed by the ai provider, separately from dusk. personal use on your own computer is free. dusk cloud plus costs $20 monthly and pro $50 monthly; that pays for a hosted computer, not ai allowance.⁷

use the always-on cost calculator for the hosting part, and the agent cost guide for other product prices. an inexpensive token calculation is not a complete monthly budget if the bot also needs a paid machine.