Claude Managed Agents Pricing: A Complete Breakdown for 2026

Claude Managed Agents pricing looks simple on paper: tokens plus a runtime fee. In practice, most teams underestimate the bill because the runtime meter, the idle-time exemption, and the list of discounts that quietly stop applying once you move from the Messages API to a managed session aren't obvious until you've read the fine print. This is for engineering and platform teams sizing out what a Claude Managed Agents deployment will actually cost before committing budget to it.

What Claude Managed Agents actually bills you for?

Anthropic bills Claude Managed Agents sessions on exactly two dimensions, according to its official pricing documentation: the tokens the agent consumes, and the time the session spends in a running state.

Every input token, output token, cache write, and cache read is billed at the same per-model rate as the standard Claude API. There's no markup for running inside a managed session. On top of that, session runtime is metered separately at $0.08 per session-hour, tracked to the millisecond, and it only accrues while the session status is running. Time spent idle (waiting on your next message or a tool confirmation) doesn't count, and neither does time spent rescheduling or after the session is terminated.

Claude Managed Agents pricing plans

There's no separate subscription tier for Managed Agents itself. You pick a model, and the session runtime fee is the same $0.08/hour no matter which model is running underneath it. Volume discounts and custom rate limits are negotiated directly with Anthropic's sales team for high-volume deployments.

What's included versus what costs extra?

A few things catch teams off guard once they start running real sessions:

• Idle time is free. A session waiting on a human response, a tool approval, or a scheduled resume doesn't burn runtime charges, only active execution time does.
• Batch API discounts don't apply. The 50% batch discount that applies to standard Messages API calls has no equivalent for Managed Agents sessions, since sessions are stateful and interactive rather than queued.
• Fast mode and data residency multipliers don't apply either. Fast mode's premium pricing and the 1.1x inference_geo: "us" multiplier are both Messages API request fields, so neither one carries over to session billing.
• Web search still costs extra. If a session triggers a web search, it's billed at the standard $10 per 1,000 searches on top of the tokens the search results generate.
• Session runtime replaces container-hour billing. If your session uses code execution, you're not billed separately for container hours the way you would be on the standalone Messages API. That cost is folded into the session runtime fee instead.

Worked example

Anthropic's own documentation walks through a one-hour coding session on Claude Opus 5 that consumes 50,000 input tokens and 15,000 output tokens:

For a higher-volume comparison: processing 10,000 support tickets on Claude Haiku 4.5, at roughly 3,700 tokens per conversation, costs approximately $37 total. The runtime fee barely moves the needle on short, high-throughput sessions; it starts to matter more on long-running agents that sit in a running state for extended periods, like an agent monitoring a queue or working through a multi-hour research task.

TrueForge: An Open-Source Alternative to Claude Managed Agents, Up to 75% Cheaper

TrueForge is TrueFoundry's open-source, vendor-neutral agent harness for teams that want more control over how their agents run in production. Instead of tying the runtime to a single model provider, TrueForge lets you bring your own models, MCP servers, and infrastructure while handling the agent loop, tool execution, context management, approvals, and sandboxing.

Where a self-hosted agent like Hermes leaves much of the production infrastructure to the developer, TrueForge provides the surrounding control plane needed to operate agents across teams and environments. This includes centralized MCP access and credentials, human-in-the-loop approvals, sandboxed execution, observability, and governance.

You can run it locally with npx @truefoundry/trueforge or deploy it for a team with Docker Compose or Helm.

TrueForge also separates the agent runtime from the model layer. This means teams can switch models or route workloads to different providers without rebuilding the agent itself.Combined with TrueFoundry's AI Gateway, teams can also apply model routing and cost controls to avoid using expensive frontier models for tasks that don't require them. The result is a middle ground between a fully managed runtime and building the entire agent infrastructure yourself: an open-source agent harness with the operational controls needed to run production agents at scale.‍

In TrueFoundry's benchmark against Claude Managed Agents, TrueForge reached roughly the same task accuracy while using about 40% as many tokens when both were run on Opus 4.8, making it about 30% cheaper per run. When the same benchmark was run with GLM-5.2 on TrueForge, it achieved the same ~11/14 task score at about $2.90 per run versus $11.80 for Claude Managed Agents, roughly 75% lower cost.

TrueFoundry also provides a second lever for reducing model costs through AI Gateway's Auto Routing. Instead of sending every request to a frontier model, Auto Routing classifies requests by complexity and routes them to different model tiers. In TrueFoundry's benchmark across 550 prompts, routing between Haiku, Sonnet, and Opus reduced cost by 69% while retaining 98% of baseline quality, and mean latency dropped from 7.6 seconds to 4.0 seconds. On production-shaped traffic, the overall cost reduction reached 80%.

These two layers address different parts of the cost equation. TrueForge reduces the overhead of running the agent itself, while model routing lets you avoid using an expensive model when the task doesn't require one. For teams running agents at scale, having both controls can matter more than the price of the model alone.

TrueForge is open source and MIT licensed, while TrueFoundry's AI Gateway adds the operational layer teams need when moving from individual agents to production: centralized model access, budgets, guardrails, credential management, and unified traces.

If you're comparing Claude Managed Agents with a more configurable architecture, TrueFoundry is worth considering when model flexibility, infrastructure control, and agent cost optimization matter alongside the agent runtime itself.

An Open-Source Alternative to Claude Managed Agents, Up to 75% Cheaper

Run production-ready AI agents on your own infrastructure with TrueForge, using your choice of models, tools, and sandbox providers.

View on GitHub

Docs

Total cost of ownership considerations

The per-session math above is only part of the real bill. Here's how the two stack up once you look past a single session, and where that comparison tends to favor which platform:

• Multi-agent scale changes the math. Claude Managed Agents charges $0.08 per session-hour on top of tokens, for every agent, every session. That's trivial for one agent, but multiply it across dozens or hundreds of concurrent sessions running continuously and it becomes a real, recurring infrastructure line item, separate from token spend, that scales with agent count rather than with actual compute used. Agent Harness carries no per-session runtime fee. Since it's open source, you pay for the infrastructure you host it on, which scales with your own compute costs rather than a per-agent vendor meter.

• Vendor lock-in has a cost even when it isn't billed directly. Claude Managed Agents only runs Claude models, so evaluating another provider later means a rebuild, not a config change. Agent Harness routes through the AI Gateway to 1,000+ LLMs across providers, so switching or mixing models is a config change, not a re-architecture, and model-level RBAC and budgets come with that access rather than being a separate build.

• Credential handling gets more expensive to manage as you grow, not just to run. Claude Managed Agents registers credentials in a vault per user per session, so the operational overhead multiplies with headcount and agent count. Agent Harness centralizes MCP credentials in the MCP Gateway with OAuth and automatic rotation: admins update a credential once and it applies to every agent using it, which costs less to operate at scale even though you're the one hosting it.

• Data residency has real requirements behind it, not just preference. Claude Managed Agents' managed cloud is US-only in beta, with EU availability planned post general availability, and no on-prem option. If air-gapped or fully on-prem deployment is a hard requirement today, that's not something Anthropic's managed offering currently supports. Agent Harness already deploys as SaaS, self-hosted, or on-prem in your own region, so that requirement is solved now rather than dependent on Anthropic's roadmap.

Line for line, the costs that compound quietly on Claude Managed Agents at multi-agent scale, the runtime meter, the single-model ceiling, per-session credentials, and the residency gap, are the ones Agent Harness is built to remove.

Conclusion

Claude Managed Agents pricing is relatively straightforward: you pay for the Claude model usage plus the additional cost of keeping an agent session active. For teams already invested in Claude and looking for a fully managed runtime, this can be a convenient way to run stateful agents without managing the underlying infrastructure.

The trade-off becomes more important as agent workloads scale. Session duration, token usage, and the number of agents you run can all add to the overall cost, while the managed runtime also limits your choice of model provider.

If you need more control over the runtime and economics of your agent stack, TrueForge provides an open-source, model-agnostic alternative. You can run agents on your own infrastructure, choose your models, and avoid a per-session-hour runtime fee while retaining control over how agents are deployed and operated.

Ultimately, Claude Managed Agents makes sense when managed infrastructure and Claude-native execution are the priority. If model flexibility, infrastructure control, and cost optimization matter more, an open agent harness such as TrueForge is worth evaluating alongside it.

FAQ

What is Claude Managed Agents pricing?

‍Claude Managed Agents bills on two dimensions: standard Claude API token rates for everything the agent reads and generates, plus a flat $0.08 per session-hour for runtime, metered only while the session is actively running. There's no separate subscription fee for the managed runtime itself.

Is Claude Managed Agents free?

‍No. It uses the same token pricing as the standard Claude API, plus the session runtime fee. New accounts get a small amount of free credit to test it, but there's no ongoing free tier for production use.

Does Agent Harness cost anything to run?

‍The harness itself is open source, so there's no license fee. You pay for the infrastructure you self-host it on and for whatever model or MCP tool calls your agents make, the same way you would with any self-hosted framework.

Does TrueFoundry support MCP and AI agents?

‍Yes. TrueFoundry includes an MCP Gateway, an Agent Gateway, and an MCP and Agents Registry with tool-level access control, so agents from any framework can be deployed and governed through one control plane.

Does TrueFoundry integrate with my existing observability stack?

‍Yes. The platform is OpenTelemetry-compliant and plugs into Grafana, Datadog, Prometheus, or your existing stack, tracing every request from prompt through tool and model execution.

Related reading

• What Is an Agent Harness?: the infrastructure layer underneath managed and self-hosted agents alike
• Claude Managed Agents vs Hermes Agent: how a fully managed runtime compares to a self-hosted alternative
• LangGraph Pricing: A Complete Breakdown for 2026: how a different agent framework's hosting costs stack up
• AI Agent Observability: Monitoring and Debugging: what to track once you're running agents in production