Codex does not have one permanent per-task price: access is included at different levels in eligible ChatGPT plans, and additional use can draw from purchased credits according to a current token-based rate card. Task size, model and surface affect consumption, so check the live rate card and account usage before budgeting client work.
- Best for
- Developers and teams who need to understand Codex cost controls before relying on it for recurring repository work.
- Not suitable for
- Anyone seeking a guaranteed number of tasks, a permanent copied rate table or an unlimited-use promise.
- Bottom line
- Use included access for a measured pilot, set a budget for extra credits and track cost by task. Do not quote a client from the plan name alone.
- This guide is based on official sources checked on 2026-08-01, not a sponsored brief or an affiliate relationship.
- No account was created and no output quality, speed, reliability, billing, deployment or support benchmark was performed.
- Plan names, models, credits and limits can change; verify the current official page and account screen before paying.
- Generated research, documents, code and applications still require source, security and human review.
What this article evaluates
OpenAI distributes Codex through ChatGPT plans and enterprise arrangements rather than a single simple task pack. Official guidance distinguishes included limits, optional credits and token-based rate-card usage. A small edit and a long agent task can consume different amounts because context, model and generated work differ.
This is an independent, non-affiliate article. UseAIVisora does not currently receive a commission from this product. That status is separate from the editorial conclusion and may change only if a future approved destination is added through the site's controlled affiliate system.
The assessment is designed for a practical buying or workflow decision. It separates what the vendor documents from what was not tested, avoids a numeric rating, and does not convert model specifications into a promise of better results.
Decision table
| Area | Documented position | What to verify |
|---|---|---|
| Included access | Varies by ChatGPT plan | Current plan page and account limit |
| Extra credits | Available for eligible users after included use | Purchase and auto top-up settings |
| Rate card | Token-based credits by model and traffic type | Live page on the actual use date |
| Task cost | Depends on context, output and model | Measure representative tasks |
| Team billing | Business and enterprise rules can differ | Workspace terms and administrator controls |
| Client billing | Not a guaranteed flat task cost | Quote with a buffer and human review time |
The table is a verification map, not a product score. A feature is useful only when it improves a specific deliverable without creating unacceptable cost, privacy or review work.
Pricing, plans and usage
The official Codex rate card is the authoritative current reference and can change. It lists credit consumption based on model input, cached input and output. OpenAI's plan guidance says Plus and Pro users can purchase credits after included limits, while business arrangements have their own rules. This article intentionally uses 'view current rate card' instead of freezing a volatile table into evergreen copy.
Do not plan a client deadline around the maximum advertised allowance. Usage systems can include rolling limits, shared credits, context-dependent consumption or separate infrastructure costs. Record the actual plan, model, region and date used for any cost comparison. If a vendor shows a rapidly changing amount, use the current-offer or current-rate page instead of copying it into a proposal as a guarantee.
A sensible evaluation budget includes subscription or credits, human review time, rework, deployment resources where relevant and the cost of leaving the platform. A cheap first prompt can still lead to an expensive workflow if corrections and operations are not measured.
A safe evaluation workflow
- Record the ChatGPT plan and included Codex access shown in the account.
- Choose one representative task and note its repository size and acceptance checks.
- Run it with conservative model and context choices.
- Record the credits or allowance consumed after the usage view updates.
- Repeat only enough to estimate a range, not a guaranteed rate.
- Set a cap or disable automatic extra usage if it is not needed.
- Recheck the live rate card before quoting or renewing.
Keep the trial narrow enough that failure is inexpensive. Use public, synthetic or redacted material, preserve a source of truth outside the product and record the errors that required correction. A successful demo is evidence about one demo, not proof of production reliability.
Privacy, permissions and security
Cost controls and security controls intersect. An agent that repeatedly reads a large repository, retries a failing task or uses unnecessary network tools can increase consumption and exposure. Limit context to the task, avoid secrets, inspect auto top-up or credit settings and separate production credentials from development agents.
For client work, document who approved the service, what data category is permitted, which account owns the workspace, how access is revoked and when data should be deleted. Consumer privacy toggles can be useful controls, but they do not replace a contract, data-processing agreement or professional obligation.
For code or app-building products, also inspect commands, network access, dependencies, database rules, authentication, authorization and secrets. A generated sign-in screen is not evidence that server-side access control is correct.
What was not tested
UseAIVisora did not create an account for this article. We did not submit prompts, upload files, run generated code, deploy an application, purchase a plan, consume credits, test cancellation, contact support, measure uptime or compare response speed. We also did not verify a vendor claim through a private dashboard that requires payment.
Official documentation can establish published features and policies. It cannot prove factual accuracy, code maintainability, security, customer-service quality or fit for a particular client's contract. Those claims remain unresolved and are excluded from the recommendation.
Strengths
- Included plan access supports an initial pilot
- A public live rate card explains additional consumption
- Credits can extend use without an immediate plan change
- Task-level measurement supports better budgeting
Limitations
- No universal task count
- Rates and plan access can change
- Long or repeated tasks can consume more
- Billing behaviour was not independently tested
Best for
Developers and teams who need to understand Codex cost controls before relying on it for recurring repository work. The strongest purchase case is a repeated task with an observable baseline: time spent, corrections required, sources verified, credits consumed and final review effort.
Not suitable for
Anyone seeking a guaranteed number of tasks, a permanent copied rate table or an unlimited-use promise. Delay payment when the use case is still vague, when confidential data cannot be supplied under the applicable terms, or when nobody can inspect the output.
Related UseAIVisora guides
Continue with OpenAI Codex review, Codex interface comparison, safe Codex repository workflow. These links connect related decisions rather than repeating keywords, and every linked article has its own research basis and fact-check date.
Final recommendation
Use included access for a measured pilot, set a budget for extra credits and track cost by task. Do not quote a client from the plan name alone. Recheck purchase-critical details on the official site because fast-moving AI products can change models, interfaces, limits and prices after this fact-check date.
Useful FAQs
Frequently asked questions
Is Codex Pricing, Credits and Usage Limits Explained free to try?
Availability and free access depend on the current official plan and region. Use the linked plan page and treat any free allowance as variable rather than a guaranteed commercial trial.
Is this article sponsored or affiliated?
No. This article has no affiliate product configured and no commission-bearing call to action.
Were the product and its results tested hands-on?
No. The article is based on official sources checked on 2026-08-01. Quality, accuracy, speed, reliability, billing, deployment and support were not independently tested.
Can I use it with confidential client work?
Only after checking the contract, account terms, privacy controls, data location, retention and required approval. Begin with public, synthetic or redacted data.
Does the documented feature guarantee a correct result?
No. Context size, agent access, research tools and deployment features describe capability, not guaranteed accuracy, security or business results.
How should I decide whether to pay?
Measure one repeated task on available access, include human review and exit costs, then compare the result with the current plan and usage terms.
Official sources reviewed
Material claims were checked on 2026-08-01 against Codex with a ChatGPT plan, Codex rate card, Codex credits, ChatGPT pricing, Codex flexible pricing for teams, Codex app announcement. The matching research note records the pricing structure, limitations, unresolved claims, hands-on status and publication recommendation.
