Category: AI Strategy

If you’re considering running Claude Managed Agents around the clock, you want a number. Not “it depends.” An actual number you can put in a budget. Here’s the math, worked out by scenario, with the honest caveats about where the real costs are.

The Formula

Total monthly cost = (Active session hours × $0.08) + token costs + optional tool costs

The $0.08/session-hour charge only applies during active execution. Idle time — waiting for input, tool confirmations, external API responses — doesn’t count. This matters significantly for 24/7 workloads, because very few agents are active 100% of the time even when “running around the clock.”

The Maximum Theoretical Cost

Scenario: Agent running continuously, zero idle time, 24 hours a day, 30 days a month.

• Session runtime: 24 hrs × $0.08 × 30 days = $57.60/month
• Token costs: separate, highly variable (see below)

$57.60/month is the ceiling on session runtime charges. You cannot pay more than this in session fees under any 24/7 scenario. But here’s the reality: that ceiling assumes zero idle time across the entire month, which doesn’t describe any real production agent.

Realistic 24/7 Scenarios

Monitoring Agent (High Idle Ratio)

Runs continuously watching for triggers — error alerts, specific data patterns, incoming requests. Activates on trigger, processes, returns to monitoring state.

• Assumption: 5% active execution time (watching 95% of the time, executing 5%)
• Active hours: 24 × 30 × 0.05 = 36 hours/month
• Session runtime: 36 × $0.08 = $2.88/month
• Token costs: low — moderate bursts on trigger events
• Realistic total: $5–15/month

Customer Support Agent (Business Hours Active)

“24/7” in the sense of always-available, but actual request volume concentrates in business hours. Waits for tickets, processes them, waits again.

• Assumption: 8 hours/day active execution, 16 hours waiting
• Active hours: 8 × 30 = 240 hours/month
• Session runtime: 240 × $0.08 = $19.20/month
• Token costs: depends heavily on ticket volume and average length
• At 100 tickets/day with moderate length: likely $30–80/month in tokens
• Realistic total: $50–100/month

Continuous Autonomous Pipeline

Batch processing agent that runs continuously through a queue with minimal waiting — the closest to true 24/7 active execution.

• Assumption: 20 hours/day truly active (4 hours queue exhaustion/maintenance)
• Active hours: 20 × 30 = 600 hours/month
• Session runtime: 600 × $0.08 = $48/month
• Token costs: high — continuous processing means continuous token consumption
• This is where tokens become the dominant cost driver by a significant margin
• Realistic total: $200–500+/month (tokens dominate)

The Real Variable: Token Costs

For any 24/7 workload that’s genuinely busy, token costs will substantially exceed session runtime costs. The math:

A moderately active agent processing 10,000 input tokens and 2,000 output tokens per hour with Claude Sonnet 4.6:

• Input: 10,000 tokens × $3/million = $0.03/hour
• Output: 2,000 tokens × $15/million = $0.03/hour
• Token cost: $0.06/hour vs. session runtime of $0.08/hour — roughly equal at this volume

Scale to 100,000 input tokens and 20,000 output tokens per hour (a busy processing agent):

• Input: $0.30/hour; Output: $0.30/hour
• Token cost: $0.60/hour vs. session runtime of $0.08/hour — tokens are 7.5× the runtime charge

The session runtime fee is flat and bounded. Token costs scale with workload volume. For high-volume 24/7 agents, optimize token efficiency (prompt caching, context management, output brevity) before worrying about the session runtime charge.

Prompt Caching Changes the Token Math

If your agent has a large, stable system prompt — common in agents with extensive tool definitions or knowledge bases — prompt caching dramatically reduces input token costs. Cache hits cost a fraction of base input rates. For a 24/7 agent with a 20,000-token system prompt hitting the same context repeatedly, caching that prompt can cut input costs by 80–90%. The session runtime charge is unchanged, but the total cost picture improves significantly.

The Budget Summary

Complete pricing reference: Claude Managed Agents Pricing Guide. How idle time affects billing: Idle Time and Billing Explained. All questions: FAQ Hub.

The most counterintuitive thing about Claude Managed Agents pricing is what you don’t pay for. Most people, when they hear “$0.08 per session-hour,” mentally model a virtual machine running continuously. That’s the wrong mental model. Here’s the right one, and why it matters for your bill.

The Core Distinction: Active vs. Idle

Managed Agents session runtime only accrues while your session’s status is running. The session can exist — open, initialized, capable of continuing — without accumulating runtime charges when it’s not actively executing.

The specific states that do not count toward your $0.08/hr charge:

• Time spent waiting for your next message
• Time waiting for a tool confirmation
• Time waiting on an external API response your tool is calling
• Rescheduling delays
• Terminated session time

This is a meaningful architectural decision by Anthropic. They’re billing on what actually taxes their compute — active execution — not on session existence or wall-clock time.

Why This Is Different From How You Might Expect Billing to Work

Compare three billing models:

Virtual machine billing (what this is not): You pay for every hour the instance exists, whether it’s idle or saturated. A VM running 24/7 with 10% actual utilization still costs 24 hours/day.

Lambda/function billing (closer analogy): AWS Lambda bills on execution duration and invocation count — you pay when code actually runs, not when a function is “available.” Idle Lambda functions cost nothing.

Managed Agents billing (what this actually is): Closer to Lambda than VM. You pay $0.08 per hour of active execution. A session that runs for 2 hours of wall-clock time but has 90 minutes of waiting costs $0.08 × 1.5 hours = $0.12, not $0.08 × 2 hours = $0.16.

A Real Scenario: The Human-in-the-Loop Agent

Consider an agent that processes your inbox for action items and waits for your approval before sending replies. Wall-clock time: 4 hours open during your workday. Actual active execution: 20 minutes of processing across that 4-hour window, with the rest spent waiting for your review decisions.

• VM billing equivalent: 4 hours × rate = significant charge
• Managed Agents billing: 20 minutes × $0.08/hr = $0.027

The difference is real. For interaction-heavy agents where the agent frequently waits for human decisions, the idle-time exclusion significantly reduces costs versus a naive per-hour model.

A Real Scenario: The Autonomous Batch Agent

Now consider an agent running a fully autonomous content pipeline — no human checkpoints, just continuous execution through a queue. Wall-clock time and active execution time are nearly identical because the agent never waits.

• A 2-hour autonomous batch: 2 hours × $0.08 = $0.16

Here, the idle-time model provides no benefit — the agent has no idle time. The billing is effectively equivalent to per-hour pricing because execution is continuous.

Code Execution Containers Are Included

One more billing nuance worth knowing: when your agent runs code, the execution happens in sandboxed Linux containers. These containers are not separately billed on top of session runtime. The $0.08/hr covers both the session runtime and the container execution. This is explicitly documented by Anthropic and represents meaningful savings if your agent is doing significant code execution work — you’re not paying twice.

What This Means for Workload Design

If you’re designing agent workflows and have the choice between architectures, the billing model creates a useful signal:

• Agents that wait on humans: Metered billing is favorable — you only pay for the actual reasoning and execution time, not the human decision time
• Fully autonomous agents: Billing approaches equivalent to per-hour rates — optimize these on token efficiency, not idle reduction
• Scheduled batch agents: Natural fit — run when needed, terminate when done, no idle accumulation

The 24/7 Agent Math

For anyone doing the 24/7 always-on calculation: the maximum theoretical runtime exposure is 24 hrs × $0.08 × 30 days = $57.60/month in session fees. But a 24/7 agent with zero idle time is rare in practice. Agents that sleep between triggers, wait on external data, or hold for human decisions have meaningful idle windows that reduce the actual charge below the theoretical ceiling.

Full monthly cost analysis: The Real Monthly Cost of Running Claude Managed Agents 24/7. Pricing reference: Complete Pricing Guide. All questions: FAQ Hub.

When Anthropic launched Claude Managed Agents, Notion was one of four launch partners. That detail got buried in the announcement. Here’s what it actually means for people who use Notion for knowledge work, and why “Notion voice input desktop” keeps showing up as a query against a Managed Agents page.

Short answer: Managed Agents in Notion is an ambient intelligence layer. It’s not a chatbot in a sidebar. It’s an agent that watches your workspace and acts — without you directing every step.

What the Notion Integration Actually Does

Notion’s Claude Managed Agents integration runs as a persistent background agent with access to your workspace. The practical capabilities, as documented at launch:

• Autonomous page updates: The agent can read, summarize, and rewrite Notion pages without manual triggers. You set a task; it works through it.
• Cross-database synthesis: Pull data from multiple Notion databases, synthesize it, and write outputs to a target page or database entry
• Meeting note processing: Ingest raw meeting notes and produce structured summaries, action items, and task entries in your project database
• Workflow automation: Trigger actions based on database property changes — a status update in one database can kick off agent work in another

The key difference from Notion AI (which Notion has had for some time): Notion AI is request-response. You ask it something; it answers. Managed Agents in Notion can be configured to run autonomously on a schedule or on trigger, keep working through multi-step tasks, and report back when done. It’s closer to a background employee than an on-demand assistant.

Why This Showed Up in Search as “Notion Voice Input Desktop”

This is worth explaining, because that query cluster is real and mildly interesting. The Managed Agents announcement included voice input functionality — the ability to interact with agents via voice in some contexts. People searching “notion voice input desktop” and “notion ai voice input desktop” were looking for whether this voice capability existed in the desktop client for Notion specifically.

The honest answer as of April 2026: voice input capabilities are in preview or context-dependent. Verify current availability in Notion’s desktop client against their current documentation — this is an area that may have evolved since launch.

The “Decoupled Brain and Hands” Model Applied to Notion

Anthropic describes their Managed Agents architecture as decoupling the brain (Claude, the reasoning layer) from the hands (the sandboxed containers where actions execute). In Notion’s context, this maps cleanly:

• The brain reads your Notion workspace, understands context, makes decisions about what to do
• The hands execute — writing to pages, updating database entries, moving content between sections

The brain and hands operate independently. The agent can reason about what your project needs without being tightly coupled to the specific API calls that will implement it. This matters because it means the agent can handle ambiguity — “clean up the Q2 notes and create action items” is a goal, not a procedure, and the agent figures out the procedure.

What You Actually Configure

To run Claude Managed Agents in Notion, you’re defining:

• Task definition: What the agent is supposed to accomplish (in natural language or structured format)
• Tool access: Which Notion databases, pages, and capabilities the agent can read and write
• Guardrails: What the agent cannot do — pages it can’t modify, actions it must confirm before taking
• Trigger: When the agent runs — on schedule, on database trigger, or on demand

You don’t write the orchestration logic. Anthropic’s infrastructure handles session management, state persistence, and error recovery. If the agent hits an error mid-task, it checkpoints and recovers — you don’t lose progress.

The Practical Cost of Running Notion Agents

Using Managed Agents in Notion triggers the same billing as any Managed Agents session: standard token rates plus $0.08/session-hour of active runtime. For typical knowledge work tasks:

• A daily meeting summary agent running 15 minutes of active execution: ~$0.02/day in runtime (~$0.60/month), plus token costs for the volume of notes processed
• A weekly database synthesis task running 45 minutes: ~$0.06/run

For most knowledge workers, the session runtime cost is negligible — the token costs (driven by how much content the agent reads and writes) are the actual variable to model. See the complete pricing reference for worked examples.

Asana and the Broader Pattern

Asana was also a Managed Agents launch partner, and the integration pattern is similar: an agent that can read project data, update task statuses, move cards, and generate project summaries without constant human direction. The launch partner list (Notion, Asana, Rakuten, Sentry) suggests Anthropic targeted three categories: knowledge management (Notion), project management (Asana), enterprise operations (Rakuten), and developer tools (Sentry).

That’s a deliberate wedge. If agents can handle the administrative layer of these four categories, the surface area for autonomous business work expands significantly.

What This Means for How You Work

The honest use case for most people reading this: you have a Notion workspace with databases that need regular synthesis, and you’re currently doing that manually. Managed Agents is the path to automating that synthesis without building and maintaining a custom integration.

The constraint worth naming: you’re running your workspace data through Anthropic’s infrastructure. That’s the trade-off. For most knowledge work, the data sensitivity concern is low. For anything involving client data, legal documents, or proprietary strategy — read Anthropic’s data handling terms before configuring access.

For the full Managed Agents setup and pricing context: Claude Managed Agents: Every Question Answered. For the enterprise deployment pattern: How Rakuten Deployed 5 Enterprise Agents in a Week.

You opened this tab because you need a number you can actually use. Not a vibe, not “it depends.” A real pricing breakdown you can put in a spreadsheet, a budget request, or a Slack message to your CTO.

This is that page. Every pricing variable for Claude Managed Agents in one place, verified against Anthropic’s current documentation as of April 2026. Bookmark it. The beta will update; so will this.

The Two Cost Dimensions

Claude Managed Agents bills on exactly two dimensions: tokens and session runtime. Every pricing question you have collapses into one of these two buckets.

Dimension 1: Token Costs

These are identical to standard Claude API pricing. You pay the same rates you’d pay calling the Messages API directly. No Managed Agents markup on tokens. Current rates for the models most commonly used in agent work:

• Claude Sonnet 4.6: ~$3/million input tokens, ~$15/million output tokens
• Claude Opus 4.6: higher rates apply — check platform.claude.com/docs/en/about-claude/pricing for current figures
• Prompt caching: same multipliers as standard API — cache hits dramatically reduce input token costs on long sessions with stable system prompts

The implication: a token-heavy agent with a large system prompt that runs the same context repeatedly benefits significantly from prompt caching, and that benefit carries over unchanged into Managed Agents.

Dimension 2: Session Runtime — $0.08/Session-Hour

This is the Managed Agents-specific charge. You pay $0.08 per hour of active session runtime, metered to the millisecond.

The critical word is active. Runtime only accrues while your session’s status is running. The following do not count toward your bill:

• Time spent waiting for your next message
• Time waiting for a tool confirmation
• Idle time between tasks
• Rescheduling delays
• Terminated session time

This is not how you’d bill a virtual machine. It’s closer to how AWS Lambda bills — you pay for execution, not reservation. An agent that “runs” for 8 hours but spends 6 of those hours waiting on human input has a very different bill than one running continuous autonomous loops.

Optional Tool Costs

Web Search: $10 per 1,000 Searches

If your agent uses web search, each search costs $10/1,000 — that’s $0.01 per search. For most agents, this is negligible. For a research agent running hundreds of searches per session, it becomes a line item worth modeling separately.

Code Execution: Included in Session Runtime

Code execution containers are included in your $0.08/session-hour charge. You’re not separately billed for container hours on top of session runtime. This is explicitly stated in Anthropic’s docs and represents meaningful savings versus provisioning your own compute.

Worked Cost Examples

Example 1: Daily Research Agent

Runs once per day. 30 minutes of active execution. Processes 10 documents, outputs a summary report. Moderate token volume.

• Session runtime: 0.5 hrs × $0.08 = $0.04/day (~$1.20/month)
• Tokens (estimate): 50K input + 5K output with Sonnet 4.6 = ~$0.23/run (~$7/month)
• Total: ~$8–10/month

Example 2: Weekly Batch Content Pipeline

Runs 3x/week. 2-hour active sessions. Processes multiple documents, generates structured outputs.

• Session runtime: 2 hrs × $0.08 × 12 sessions/month = $1.92/month
• Tokens: depends on content volume — typically $10–40/month
• Total: ~$12–42/month

Example 3: Customer Support Agent (Business Hours)

Active during business hours, handling tickets. 8 hours/day active, 5 days/week.

• Session runtime: 8 hrs × $0.08 × 22 days = $14.08/month in runtime
• Tokens: highly variable by ticket volume — the dominant cost driver at scale
• Runtime cost alone: ~$14/month — tokens are likely 5–20x this depending on volume

Example 4: 24/7 Always-On Agent

The maximum theoretical runtime exposure. Continuous operation, no idle time.

• Session runtime: 24 hrs × $0.08 × 30 days = $57.60/month
• In practice, no agent has zero idle time — real cost will be lower
• Token costs at this scale become the dominant factor by a wide margin

Anthropic’s Official Example (from their docs)

A one-hour coding session using Claude Opus 4.6 consuming 50,000 input tokens and 15,000 output tokens: session runtime = $0.08. With prompt caching active and 40,000 of those tokens as cache reads, the token costs drop significantly. The runtime charge stays flat at $0.08 regardless of caching.

What’s Not Billed in Managed Agents

A few things that might seem like costs but aren’t:

• Infrastructure provisioning: Anthropic handles hosting, scaling, and monitoring at no additional charge
• Container hours: Explicitly not separately billed on top of session runtime
• State management and checkpointing: Included in the session runtime charge
• Error recovery and retry logic: Anthropic’s infrastructure problem, not yours

Rate Limits

Managed Agents has specific rate limits separate from standard API limits:

• Create endpoints: 60 requests/minute
• Read endpoints: 600 requests/minute
• Organization-level limits still apply
• For higher limits, contact Anthropic enterprise sales

How to Access Managed Agents Pricing

Managed Agents is available to all Anthropic API accounts in public beta. No separate signup, no premium tier gate. You need the managed-agents-2026-04-01 beta header in your API requests — the Claude SDK adds this automatically.

For high-volume agent applications, Anthropic’s enterprise sales team negotiates custom pricing arrangements. Contact them at [email protected] or through the Claude Console.

The Pricing Signals Worth Noting

Anthropic recently ended Claude subscription access (Pro/Max) for third-party agent frameworks, requiring those users to switch to pay-as-you-go API pricing. This signals a deliberate strategy: consumer subscriptions are for human-paced interactions; agent workloads route through the API. The $0.08/session-hour rate exists in that context — it’s infrastructure pricing for compute that runs beyond human attention spans.

The session-hour model also signals something about Anthropic’s infrastructure cost structure. They’re pricing on active execution time because that’s what actually taxes their systems. Idle sessions don’t cost them much; active agents do. The billing model follows the actual resource consumption pattern.

Frequently Asked Questions

For the full session-hour math worked out by workload type, see: Claude Managed Agents Pricing, Decoded: What a Session-Hour Actually Costs You. For the build-vs-buy infrastructure comparison: Build vs. Buy: The Real Infrastructure Cost. For enterprise deployment patterns: Rakuten Stood Up 5 Enterprise Agents in a Week.