API boundary
ChatGPT plan access, Codex credits, and OpenAI API token billing are separate systems. API usage should be modeled from OpenAI API pricing, not ChatGPT plan allowances.
Pricing
Compare Codex access, GPT-6.1 Sol workhorse integration, Astra frontier reasoning, Pro 100/200/500, shared Work/Codex allowance, purchased credits, and API-key use.
Buyer guide
Check who bills you, how usage is metered, and which caveats apply before choosing an access path.
API boundary
ChatGPT plan access, Codex credits, and OpenAI API token billing are separate systems. API usage should be modeled from OpenAI API pricing, not ChatGPT plan allowances.
Tracks
Use the ChatGPT route when you want first-party Codex surfaces and plan-based usage limits instead of a separate developer-platform bill.
Best for: Solo developers and teams already choosing a ChatGPT subscription tier.
Avoid if: You need API keys, CI automation, or a separately metered platform budget.
Use the current model-specific Codex credit rate card for Astra, GPT-6.1 Sol, GPT-6 Sol and GPT-5.6, including the applicable subscription and Fast-mode modifiers. API dollar rates are a different meter.
Best for: Buyers modeling heavier Work or Codex sessions, parallel tasks, max reasoning, or ultra multi-agent runs.
Avoid if: You only need a simple yes/no answer about whether your ChatGPT plan unlocks Codex.
Use Business when admin controls, workspace credits, and existing Codex-seat eligibility matter more than a single individual subscription tier. New Business workspaces should not assume they can add Codex-only seats.
Best for: Teams using standard Business ChatGPT seats, existing eligible Codex-only seats, or Enterprise/Edu flexible pricing conversations.
Avoid if: You are a solo user without workspace governance needs.
Use API pricing when you are building custom coding-agent systems, product integrations, or CI workflows with API keys.
Best for: Engineering teams with programmatic automation and separate platform spend.
Avoid if: You mainly want human-driven repository work inside Codex product surfaces.
Access paths
Each access path shows who owns the bill and whether access is bundled, separately metered, sold as an add-on, or handled through sales.
Codex is included across current ChatGPT plans on desktop, web, CLI, and IDE surfaces; ChatGPT Work follows the same usage structure.
Best for: Developers who want subscription-backed Codex work with the models actually available to their account.
Boundary: A Codex entitlement is not an Astra entitlement. The Astra rollout lists Plus, Pro, Business and Enterprise; eligible use draws from existing allowance or workspace billing. Confirm any legacy Codex-seat eligibility separately.
Open ChatGPT pricing contextUse first-party ChatGPT Work and Codex surfaces for interactive agent work with shared plan limits and credits.
Best for: Interactive repository work, code review, and agent sessions managed by OpenAI product UX.
Boundary: This route is plan- and credit-based. Work and Codex share the agentic usage pool; API-key usage remains separate.
Open Codex pricing contextUse gpt-6-astra only when available to your API account, or retain an appropriate GPT-5.6 model. Budget against the current API context tier, input/output and cache rates, separately from Codex credits.
Best for: Programmatic coding agents, internal tools, and product integrations.
Boundary: API spend is separate from ChatGPT subscription allowances and should be modeled by tokens or request units.
Open Codex pricing contextWatchouts
These are the boundary conditions and purchase traps worth checking before you optimize for the lowest headline number.
Codex can be reached through ChatGPT plans, but this page should not duplicate the full ChatGPT plan table. Open the canonical ChatGPT pricing page for exact subscription tiers.
Buying or consuming Codex credits extends plan-based Codex usage. It does not prepay or discount OpenAI API token bills.
Standard ChatGPT Business seats include Codex. A workspace can manage legacy Codex-only seats only if it had a seat before June 24, 2026 or a pending invite as of June 24; new workspaces cannot add a first Codex-only seat.
OpenAI publishes different Astra and GPT-5.6 credit rates. Its per-task comparisons are estimates, not fixed limits or billing multipliers; confirm token mix, context, settings and the applicable allowance or purchased-credit rate.
Editorial pricing notes
Plan caveats, contract terms, and feature-access limits that can change what you actually pay.
Codex pricing is organized around three distinct financial tracks rather than a single standalone software license:
platform.openai.com (such as integrating OpenAI models into custom CI/CD pipelines, IDE plugins, or internal tools) are billed strictly on a metered per-token basis. ChatGPT subscriptions and Codex workspace fees never cover API token invoices.Legacy Codex-only Business standalone seats (from prior to the 2026 workspace consolidation) remain active only for organizations established prior to June 2026; all new teams subscribe through ChatGPT Business or Enterprise plans.
The table below outlines the pricing, included coding allowances, model capabilities, and spending controls across the primary ways developers access Codex.
Access Route | Monthly Price | Included Codex Features | Autonomous Cloud Tasks | Frontier Model Access | Team Governance | API Token Separation |
|---|---|---|---|---|---|---|
ChatGPT Plus | $20 / month | Interactive coding & code interpreter | Expanded Codex usage | GPT-6 Astra, Sol and Luna; GPT-5.6 Sol and Terra | Individual account only | Separate billing |
ChatGPT Pro | $100, $200 or $500 / month | High-compute coding & deep analysis | Longer Codex sessions; Pro 500 adds Ultrafast for GPT-6 Astra and GPT-6.1 Sol | Pro reasoning powered by GPT-6 Astra; GPT-6.1 Sol; GPT-5.6 Sol Pro | Individual account only | Separate billing |
ChatGPT Business | $25 / seat / mo ($20 annual) | All Codex features & shared GPTs | Workspace usage plus purchasable credits | All ChatGPT models | Central admin + spend controls | Separate billing |
ChatGPT Enterprise | Custom contract | Custom compute allocation | Uncapped priority tasks | Custom endpoints & SLA | SSO, SCIM, ZDR, audit logs | Separate billing |
OpenAI Platform API | Pay-as-you-go | Raw model completions & tool calls | N/A (Build your own) | All API models | API organization keys | Metered per million tokens |
Codex compute consumption falls into two distinct operational paradigms, each with different cost implications:
When a developer uses Codex inside ChatGPT to refactor a function, explain an unfamiliar code snippet, or generate unit tests, compute is treated as standard chat inference.
When Codex is tasked with resolving a complex engineering issue—such as cloning a repository, installing dependencies, editing multiple interrelated files, running unit tests, and iteratively debugging build failures—it executes inside a dedicated, containerized cloud sandbox.
Codex Billing and Usage Flow
Developer triggers coding workflow
In team environments, unmonitored autonomous agent loops can inadvertently trigger escalating cloud bills. OpenAI provides structured administrative guardrails within ChatGPT Business and Enterprise consoles:
A frequent question from engineering organizations is whether paying for ChatGPT Plus or Business covers the API tokens needed for developer tools like Cursor, Cline, or custom CLI scripts.
chatgpt.com grant access to graphical web interfaces, Canvas, and official mobile apps. They never include API token credits.sk-... API key for external IDE integrations or custom backend services, you must create an account at platform.openai.com, add a payment card, and pre-purchase API balance tiers.When budgeting for developer productivity tools, organizations should compare the total cost of ownership across major coding assistants:
Tool | Entry Monthly Price | Included Coding Allowance | Overage Model | Unique Architectural Advantage |
|---|---|---|---|---|
OpenAI Codex (ChatGPT) | $20 (Plus) / $25 (Business) | Full Canvas + sandboxed tasks | Supplemental credit packs | Native web Canvas + cloud agent execution |
Cursor | $20 / month | 500 Fast Requests + unlimited slow | ~$0.10 / fast request (Hard cap) | VS Code-forked IDE + Tab autocomplete |
GitHub Copilot | $10 (Pro) / $19 (Business) | Unlimited completions + chat | Separate AI Credits ($0.01) | Deep GitHub repo & PR integration |
Claude Code | $20 (Claude Pro) or API | Pro/Max OAuth or token billing | Direct API token meter | Terminal-native REPL + MCP integration |
To choose the right Codex access path for your workflow:
Evidence boundary
Editorial guidance grounded in official product sources.
FAQ
Go at $8 per month in the US is the lowest paid Codex entry. Plus at $20 per month is the first dependable tier, providing GPT-6.1 Sol and GPT-6 Sol for agentic coding and GPT-6 Astra for frontier reasoning, with expanded access on Pro.
Codex offers GPT-6.1 Sol as its workhorse model, released 2026-09-29 and listed on Plus and Pro, with GPT-6 Sol still available and GPT-6 Astra for frontier reasoning. GPT-6.1 Sol uses 50 credits per 1M input, 2.5 cached and 250 output tokens, the same as GPT-6 Sol except cached input (5). Plus includes focused weekly usage, while Pro and Business tiers draw from larger allowances and workspace credit pools.
No. Only a Business workspace that had a Codex seat before June 24, 2026 or a pending invite as of June 24 can continue managing or adding Codex-only seats. New workspaces cannot add a first Codex-only seat.
No. ChatGPT plan access and API token billing are separate systems. If you use Codex with an API key or build your own workflows, you should expect a separate API bill.
OpenAI lets eligible plans extend Codex usage with credits. That keeps you on the plan-based Codex path, which is still different from paying API token rates directly.
No. ChatGPT subscription access and OpenAI API billing are separate. If a workflow uses an API key, model that cost from the OpenAI API pricing path rather than the ChatGPT seat price.
For individual review work, start with the lowest ChatGPT plan that provides enough usage. For teams, compare standard Business controls and workspace credits; only workspaces with a seat before June 24, 2026 or a pending invite as of June 24 should consider legacy Codex-only seats. API-based automation remains separate.
Internal links
Pair the pricing snapshot with alternatives and the full profile page.
Open direct comparison pages before choosing a plan.
Sanity-check nearby tools before committing to a pricing tier.