Pricing Plans
- 150 Compute Tokens included
- Create your own Environments
- Work with any documents
- Integrate with all your apps
- Best-in-class Research models
- Best-in-class image models
- Schedule Tasks
- API Access
- 1.5k Compute Tokens included
- Access to premium models
- Create your own Agents
- Create your own Environments
- Work with any documents
- Integrate with all your apps
- Best-in-class Research models
- Best-in-class image models
- Schedule Tasks
- API Access
- 5k Compute Tokens included
- Access to premium models
- Create your own Agents
- Create your own Environments
- Work with any documents
- Integrate with all your apps
- Best-in-class Research models
- Best-in-class image models
- Schedule Tasks
- API Access
- Bring your own inference endpoint
- Usage-based resources after included credits
- Shared workspaces and resources
- 15k Compute Tokens included
- Access to premium models
- Create your own Agents
- Create your own Environments
- Work with any documents
- Integrate with all your apps
- Best-in-class Research models
- Best-in-class image models
- Schedule Tasks
- API Access
- Bring your own inference endpoint
- Usage-based resources after included credits
- Shared workspaces and resources
- Advanced governance and priority support
Need more Compute Tokens this month?
Buy one-time Compute Token packs when you want more headroom without changing your subscription. Included monthly credits are always used first. Purchased add-ons stay on the account until they are consumed.
One-time extra budget for short bursts, overages, and deadline weeks.
A larger top-up for heavier agent workloads and multi-step automation.
High-volume one-time capacity for production spikes and larger pipelines.
Persistent resource pricing
Included monthly credits are always used first. On Team and Enterprise, if usage-based billing is enabled, persistent resources can continue after included credits are exhausted at the rates below. The default computer profile is Lite; heavier workloads can scale up to Standard, Power, or Desktop.
CLI-first environment for everyday coding, prompts, and automation.
Balanced computer for most build, test, and agent execution workflows.
Higher CPU and memory for heavier repos, builds, and multi-step automation.
GUI-enabled computer for browser automation, visual QA, and desktop workflows.
Compute Tokens in Real Terms: Tasks
Pick a task type and instantly see how many task starts each plan can handle per month.
Small follow-up using Claude Haiku 4.5 on the Lite runtime profile. Estimate basis: ~4 CT per task start on the Lite computer profile.
Individual
Team
Enterprise
Estimate Compute Tokens from both model usage and thread runtime. This gives a more realistic cost basis for managed execution on ACP. Runtime pricing follows the selected computer profile.
How Pricing Works
ACP pricing has two layers: a workspace plan with included monthly credits, and optional usage-based infrastructure on collaborative plans when you want execution to continue after credits are exhausted.
Included monthly credits
ACP tracks managed usage in Compute Tokens. This gives the platform one comparable budget across model execution, runtime minutes, and other managed infrastructure that is billed inside the product.
Included monthly credits are always used first. A single thread, computer session, or agent workflow can consume both model usage and runtime from the same plan budget.
What credits normally cover
Managed model usage for threads, agents, teams, and research flows.
Short-lived runtime for thread execution, agent work, and standard developer workflows while you are iterating in the platform.
Persistent resources have separate metered rates once you move into usage-based infrastructure billing.
Usage-based infrastructure
On Team and Enterprise, you can enable usage-based infrastructure after included monthly credits are exhausted. If metered billing is disabled, resource activity pauses when your included budget runs out.
If metered billing is enabled, workloads continue until you hit your configured spend cap. This is the right setup for always-on apps, shared team resources, and longer-running automation.
One-time Compute Token add-ons
If you hit your included monthly plan budget, you can buy a one-time Compute Token pack instead of changing your subscription immediately.
Add-ons are applied after your included monthly credits are exhausted and remain on the account until they are consumed. They are useful for launches, backfills, batch processing, and temporary spikes in demand.
Bring your own models
Team and Enterprise can connect an OpenAI-compatible inference endpoint and expose those models inside ACP. This is the right path when you want to route execution to your own infrastructure, use customer-managed credentials, or standardize on a specific inference stack.
ACP-hosted models consume included credits first and are the default path for most teams.
Team and Enterprise can route supported workloads to their own inference endpoint.
Larger deployments can combine BYOM, governance controls, spend caps, and customer-managed rollout.
Included monthly credits by plan
Get started with basic usage. Perfect for trying out the platform.
Personal access for builders who want premium models, agents, environments, and API access in one plan.
Shared access for teams with bring-your-own model endpoints and usage-based infrastructure after included credits.
Enterprise-scale access with higher included usage, team operations, and room for advanced governance and self-hosting requirements.
Plan identifiers
Use these plan identifiers in product logic, entitlement checks, and internal tooling.
Older systems may still emit historical tier IDs. ACP normalizes them before evaluating access.