[dead]
Codex pricing to align with API token usage, instead of per-message
41–50 of 212 posts
Re: Codex pricing to align with API token usage, instead of per-message
#42Is this something that is likely to also change the way Github Copilot bills? Right now the billing is message-based, not token-based. And OpenAI and Microsoft are rather opaquely intertwined in the AI space.
Re: Codex pricing to align with API token usage, instead of per-message
#43[dead]
Re: Codex pricing to align with API token usage, instead of per-message
#44So migrate to gemini now?
If you use Google's tooling but not if you need API access. API access is not in the subscriptions and uses token based pricing. For development I find that the Gemini IDE plugins that have good free usage and are included in the subscriptions aren't great. Gemini plug-in under IntelliJ is often broken, etc. The best experience is with other tools like Cline where you've had to use a developer based account which is API usage based already.
But Gemini's API based usage also has a free tier and if that doesn't work for you (they train on your data) and you've never signed up before you get several hundred dollars in free credits that expire after 90 days. 3 months of free access is a pretty good deal.
Re: Codex pricing to align with API token usage, instead of per-message
#45Earlier quoted context omitted.
There are plenty of good models on Openrouter that are very cheap, maybe it's time to experiment with alternatives.
what are some of them?
MiniMax M2.7, MiMo-V2-Pro, GLM-5, GLM5-turbo, Kimi K2.5, DeepSeek V3.2, Step 3.5 Flash (this last one is particularly cheap while still being powerful).
Re: Codex pricing to align with API token usage, instead of per-message
#46Re: Codex pricing to align with API token usage, instead of per-message
#47Is this not just about extra credit? So what's included in the subscription doesn't change - just extra credits are now token based instead of message based? (For Plus/Pro)
Yes.
> This format replaces average per-message estimates with a direct mapping between token usage and credits.
It's to replace the opaque, per-message calculation, not the subscription plan.
Re: Codex pricing to align with API token usage, instead of per-message
#48from what they wrote, they're just changing how they measure the usage; might even be a good thing if you manage your context right:
> This format replaces average per-message estimates for your plan with a direct mapping between token usage and credits. It is most useful when you want a clearer view of how input, cached input, and output affect credit consumption.
Re: Codex pricing to align with API token usage, instead of per-message
#49Earlier quoted context omitted.
It’s kind of a rug pull to effectively raise the price like 10x. I can’t afford to finish some of my projects with this change
That is okay. Ultimately, we need to know the true cost of this technology to evaluate how effectively or ineffectively it can displace the workforce that existed before it.
Agreed, this has to happen and the sooner the better.
Re: Codex pricing to align with API token usage, instead of per-message
#50For the past month, I've been claiming that $20/mo codex is the best deal in AI. Now I'm going to have to find the new best deal.
Already paying for Google photo storage, AI pro for an extra $7 is a steal with anti-gravity.
That's only good for the web based UI. If you want Gemini API access which is what this article is about then you must go the AIStudio route and pricing is API usage based. It does have a free usage tier and new signups can get $300 in free credits for the paid tier so it's I think it's still a good deal, just not as good as using the subscriptions would be.