For 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.
Codex pricing to align with API token usage, instead of per-message
61–70 of 212 posts
Re: Codex pricing to align with API token usage, instead of per-message
#62Earlier quoted context omitted.
We are exiting a hype cycle, well into the adoption curve. Subscriptions were never going to last. My next step is going to be evaluating open and local models to see if they are sufficiently close to par with frontier models. My hope is that the end of seat based pricing comes with this tech cycle. I was looking for document signing provider that doesn't charge a monthly, I only need a few docs a year.
I recently experimented creating a Python library from scratch with Codex. After I was done, I took the PRD and Task list that was generated and fed them to opencode with Qwen 3.5 running locally. Opencode was able to create the library as well. It just took about 2x longer.
Re: Codex pricing to align with API token usage, instead of per-message
#63Well, I know why. I just wanted to be snarky. It's just that trying to hide the actual price is getting a bit old. Just tell me that generating this much code will cost me $10.
Re: Codex pricing to align with API token usage, instead of per-message
#64Earlier quoted context omitted.
I recently experimented creating a Python library from scratch with Codex. After I was done, I took the PRD and Task list that was generated and fed them to opencode with Qwen 3.5 running locally. Opencode was able to create the library as well. It just took about 2x longer.
Which version of Qwen 3.5 did you use?
Re: Codex pricing to align with API token usage, instead of per-message
#65Earlier quoted context omitted.
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.
It does feel like also impact the usage meter for subscription plans?
Re: Codex pricing to align with API token usage, instead of per-message
#66Re: Codex pricing to align with API token usage, instead of per-message
#67The days of subsidized access is rapidly coming to an end.
Re: Codex pricing to align with API token usage, instead of per-message
#68Is 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)
Re: Codex pricing to align with API token usage, instead of per-message
#69For 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.
We are exiting a hype cycle, well into the adoption curve. Subscriptions were never going to last. My next step is going to be evaluating open and local models to see if they are sufficiently close to par with frontier models. My hope is that the end of seat based pricing comes with this tech cycle. I was looking for document signing provider that doesn't charge a monthly, I only need a few docs a year.
If you have an M processor then I would recommend that you ditch Ollama because it performs slowly. We get double or triple tok/s using omlx or vmlx, respectively, but vmlx doesn't have extensive support for some models like gpt-oss.
Re: Codex pricing to align with API token usage, instead of per-message
#70Earlier quoted context omitted.
Good!
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