API pricing itself might have extreme margins compared to the real cost. Anyway, in my testing the Pro 20x $200 plan gives you about $2200 API-equivalent weekly usage if you're only using GPT 5.6 Sol, so quite close to $9k-$10k/month API-equivalent, it's a bit inconsistent with cache costs.

It's very interesting that for Anthropic the $100 and $200 plans only differ 2x in weekly limits, the 5 hour limit differences are more severe. But for OpenAI, Pro 20x is, well, 4x of Pro 5x for only 2x cost. So, for example, 100% of weekly usage for Codex on a Plus ($20) account is just 5% of weekly usage for Codex on Pro 20x.

And you can calculate how much extra usage you can get from resets, and especially banked resets by purposefully using the whole quota and using your banked reset - they expire 30 days after they're given out, so if you don't use one, it just disappears.

▲

loufe 16 hours ago | parent [-]

Edit:

The $200 plan is explicitly 4x the $100 plan[1] only for "per session". That's so vague. I initially pushed back against your claim, but reading now Anthropic is not at all clear, in fact.

[1] https://support.claude.com/en/articles/11049741-what-is-the-...

	▲	dannyw 15 hours ago \| parent [-]
		Empirically it is quite easy to validate that the "20x" plan is misleading and only give you twice the weekly limits of the "5x" plan, and many people on r/ClaudeAI, etc can verify that. Anthropic is also the one often playing games with: * The "+30% tokens" tokeniser, alongside also gating token counting behind an API (versus the MIT tiktoken for OpenAI), so who knows if it's really a new tokeniser or of it's just a disguised price increase. * Prompt injections appended to API (not just Claude.ai or Claude Code!), such as <ethics_reminders>, or LCRs (long conversation reminders), which you never asked but still pay for with expensive API. You can detect this because your input_tokens, as reported by the Messages response, sometimes don't match, and are higher than your actual input. (Alternatively, for testing purposes, create a tool like `telemetry_log_anthropic_reminder` or something and instruct your system prompt to require Claude to call the tool anytime it detects any Anthropic/Claude reminder masquerading in the user input -- mostly reliable; but misses some reminders). In particular, the long conversational reminders, when incorrectly triggered by a classifier and (almost silently, unless you track tokens) appended to an API / agentic coding session, can ruin your agent's performance; and it often fires repeatedly once the classifier kicks in. If you're using Anthropic API, you need to set up metrics/logging for how often they are appending things to your prompt without your knowledge. So far I have not empirically observed prompt injection by the OpenAI API, only Anthropic APIs.