Updated November 15, 2026: Workspace Agents are no longer in the free preview described in this guide's original May coverage. OpenAI extended that period to July 6, when token-based pricing took effect. The Business release notes document the extension and billing transition.
The most useful way to think about workspace agents is not as a normal seat add-on. They are closer to a managed automation layer inside ChatGPT. So the real budgeting question is not just “How much is a seat?” It is “How often will these agents run, how much work will they do, and when do we want humans in the loop?”
The current Workspace Agents credit rate
The current credit rate card lists GPT-5.6 Workspace Agents at 100 credits per million input tokens, 10 per million cached input tokens and 500 per million output tokens. Its 5–25-credit typical-run range is an estimate, not a flat fee or cap.
Business standard seats have included shared agentic usage; purchased workspace credits can extend eligible usage after included limits. Enterprise agreement terms determine whether credit-based or USD token-based billing applies. Do not convert credits to dollars without the applicable purchase or contract terms, and do not confuse this with direct API billing.
For the historical transition, see our July 6 pricing-change report. This guide focuses on current budgeting rather than the expired preview deadline.
What you are really paying for
For most buyers, workspace agents will create three separate cost buckets.
1. Seat access
If your organization is not already on ChatGPT Business or Enterprise, the first cost is getting into the workspace product at all. For many smaller teams, that starts with ChatGPT Business. Larger rollouts will usually land in Enterprise, where pricing is negotiated.
2. Agent runtime
Agent activity is metered. Budget the actual input, cached input and output usage across a complete run, then account for the included allowance and the purchased-credit or contract terms that apply to your workspace.
3. Operational overhead
Even if the direct price looks manageable, real cost also includes admin oversight, approvals, monitoring, and workflow design. Teams that skip this part often misread their budget because they focus on model spend and ignore the work required to keep automations safe and reliable.
What Budgeting Looks Like by Team Stage
Pilot phase
In an early pilot, the main cost is usually seat access plus a measured amount of agent usage. This is the right phase to test a few narrow workflows: account research, report prep, internal ticket triage, or meeting follow-ups. The goal is not maximum automation. The goal is learning which workflows create repeatable value.
Department rollout
Once a team starts sharing agents across sales, support, finance, or operations, costs become less about experimentation and more about recurring runs. Scheduled workflows, repeated tool calls, and larger user adoption can make spend climb faster than leaders expect if they only budget for seats.
Heavy automation
If your plan is to let agents run frequent background work across tools, then the critical variable is not the sticker price of ChatGPT Business. It is total execution volume. Teams at this stage should set monthly usage caps, require approvals for sensitive actions, and separate high-frequency tasks from high-value tasks before broad rollout.
Estimate credits from workload, then measure the result
For an illustrative run with 20,000 uncached input tokens, 10,000 cached input tokens and 5,000 output tokens, the arithmetic is (0.02 × 100) + (0.01 × 10) + (0.005 × 500) = 4.6 credits. The cached input in this example is a separate category, not counted twice. Actual runs can use different quantities; an illustrative run below the typical range does not contradict an estimate.
A thousand identical runs would use 4,600 credits before accounting for the workspace's allowance. This is not a dollar quote. Forecast with measured usage from representative tasks, include failed and retried work, and compare the total against accepted outcomes.
- Separate subscription commitments, included usage and additional purchased capacity.
- Measure runs and their token mix rather than multiplying employees by a guessed flat agent fee.
- Record human review and repair time alongside usage.
- Keep approval gates on consequential actions, even when a run is inexpensive.
- Choose a pilot spending boundary and success criteria before expanding schedules.
How Workspace Agents compare with API-based agents
Both can be modeled, but they are different products and billing arrangements. Use the live API pricing page for a direct API build rather than carrying old model prices into a new estimate. For Workspace Agents, use the applicable workspace rate card and allowance.
A fair comparison includes orchestration, tool infrastructure, monitoring, permissions and maintenance. A lower model charge can be outweighed by implementation work; a managed workspace can be a poor fit if it cannot support the required workflow. Test the same acceptance criteria on both options.
When workspace agents are probably the right choice
- You want employees to use agents inside ChatGPT rather than inside a custom internal app.
- You need quick deployment without building your own orchestration and UI layer.
- You care more about internal workflow acceleration than shipping a product to external users.
- You want shared agents, admin controls, and a familiar workspace experience.
When a custom agent stack may make more sense
- You need direct control over how usage is metered and optimized in your own application.
- You want fine-grained control over models, prompts, routing, and tool policy.
- You are building customer-facing automation, not just internal productivity.
- You expect very high execution volume and want tighter control over unit economics.
What teams should do next
Pick two or three workflows with a clear owner and observable outcome. Record usage, failed attempts, completion time and review effort. Decide whether the value comes from speed, consistency or reduced manual work, then set a credit budget consistent with your workspace's actual billing terms.
The rate card now exists. The remaining uncertainty is your workload, not an unpublished universal per-run price. Keep the original pilot tasks as a comparison set when prompts, tools or models change, and expand only when measured outcomes justify the total cost.