Tag: Claude AI Pricing

  • Claude Team Plan Usage Limits & Pricing (2026)

    Claude Team Plan Usage Limits & Pricing (2026)

    Last refreshed: May 15, 2026

    Direct Answer (August 2026): Claude Team plan provides pooled, higher message limits per user (approx. 5x Pro capacity shared across the team) with a 5-seat minimum ($20–$100/seat/mo). Team accounts include administrative controls, billing consolidation, and team-wide project workspaces.

    The Claude Team plan’s usage limits changed significantly in May 2026. If you’re a Team subscriber and you haven’t noticed yet, you’re now getting substantially more capacity than you were in April — and the free tier got left behind entirely. Here’s exactly what changed, what you have now, and what it means in practice.

    Updated May 9, 2026

    Rate limits doubled for Team plan subscribers following Anthropic’s SpaceX Colossus 1 compute deal (announced May 6, 2026). Free plan excluded from all increases. This page reflects current limits.

    What Changed in May 2026: The SpaceX Rate Limit Increase

    On May 6, 2026, Anthropic announced a compute partnership with SpaceX, giving it access to SpaceX’s Colossus 1 data center. The practical result for paying subscribers came fast: rate limits doubled. Here’s the breakdown by tier:

    • Claude Code Pro and Max: 5-hour rate limits doubled
    • Team plan (all seats): 5-hour rate limits doubled
    • Seat-based Enterprise: 5-hour rate limits doubled
    • Tier 1 API customers: Max input tokens per minute increased 1,500%; max output tokens per minute increased 900%
    • Peak-hours throttling: Eliminated entirely for Pro and Max subscribers
    • Free plan: No change. Explicitly excluded from all increases.

    Source: Anthropic’s official announcement at anthropic.com/news/higher-limits-spacex.

    The 1,500% input token figure for Tier 1 API is the one that didn’t get much press coverage. That’s a 15× ceiling increase for API users who’ve been running agent pipelines and hitting hard walls. If you’ve been rate-limited during multi-step Claude Code runs, this is the change that matters most.

    Team Plan Seat Structure (Still Current)

    Stacked capacity bands for Free, Pro, Max, and API tiers without numeric RPM or TPM values
    Team plan seat structure.

    The seat types haven’t changed — just the capacity within them. The Team plan still offers two seat types that can be mixed within the same organization:

    Seat Type Annual Price Monthly Price Usage vs Pro Claude Code
    Standard$20/seat/month$25/seat/month1.25× more per sessionNo
    Premium$100/seat/month$125/seat/month6.25× more per sessionYes

    Both seat types benefit from the May 2026 doubling of the 5-hour rate limit window. A Premium seat’s 6.25× multiplier now applies to a higher baseline than it did before May 6.

    How the 5-Hour Rate Limit Window Works

    Infographic with three panels: protect the service, fair share, and cost control explaining rate limits
    How the rate-limit window works on Team.

    Anthropic uses a rolling 5-hour window for usage limits, not a daily reset. Here’s what that means practically:

    • Usage is measured across a rolling 5-hour window, not midnight-to-midnight
    • If you hit the limit, you wait for the oldest usage to roll off — not for a fixed reset time
    • Heavy burst usage depletes your window faster than spread-out usage
    • The May 2026 doubling means the ceiling within that window is now twice as high

    Peak-hours throttling — the extra restriction that kicked in during high-demand periods — is now eliminated for Pro and Max. Team plan benefits from the doubled limit floor; the throttling elimination is Pro and Max specific.

    Current Models Available on Team Plan

    As of May 2026, the Claude model lineup (verified from Anthropic’s official models page):

    Model API String Context Window
    Claude Fable 5claude-fable-51M tokens
    Claude Opus 4.8claude-opus-4-81M tokens
    Claude Sonnet 5claude-sonnet-51M tokens
    Claude Haiku 4.5claude-haiku-4-5-20251001200K tokens

    Deprecation notice: Claude Sonnet 4 and Opus 4 (original 4.0-generation, 20250514 date-string model IDs) were retired June 15, 2026. Update any API integrations before that date.

    What the Free Plan Doesn’t Get

    The May 2026 rate limit increase does not apply to free accounts. Anthropic explicitly excluded the free tier from all capacity increases tied to the SpaceX deal. Paid plans now have a substantially higher ceiling while the free ceiling stays the same. If you’re hitting limits regularly on the free tier, the May 2026 changes are pressure toward upgrading — not relief.

    Team Plan vs Pro: Which Limit Structure Fits You?

    Decision map from daily chat, shipping products, or buying for a company to Free/Pro, API, or Team/Enterprise
    Team vs Pro — which limit structure fits.
    • Individual power user: Pro ($20/month) with throttling eliminated is a strong option.
    • Team with Claude Code needs: Team Premium seats ($100/seat/month annually) give Claude Code access, 6.25× multiplier, and the doubled 5-hour window.
    • Team without Claude Code needs: Standard Team seats ($20/seat/month annually) for shared access at higher limits than individual Pro.

    Frequently Asked Questions

    Did the Team plan rate limits actually double in May 2026?

    Yes. Anthropic confirmed the 5-hour rate limit doubled for Team plan subscribers following the SpaceX Colossus 1 compute deal announced May 6, 2026. This applies to both Standard and Premium seats.

    Does peak-hours throttling elimination apply to Team plan?

    The peak-hours throttling elimination was announced specifically for Pro and Max subscribers. Team plan benefits from the doubled rate limit floor; throttling elimination was not announced for Team.

    What happens when I hit a Team plan usage limit?

    Claude notifies you that you’ve reached your usage limit. With the 5-hour rolling window, you can continue once older usage rolls off — you’re not waiting for a midnight reset. Burst usage depletes the window faster than spread usage over the same period.

    Are Claude Sonnet 4 and Opus 4 still available on Team?

    They remained available until June 15, 2026, when they were retired. Since then, the active lineup has been Fable 5, Opus 4.8, Sonnet 5, and Haiku 4.5.

    Does the 1,500% Tier 1 API increase apply to Team plan API usage?

    The 1,500% input and 900% output token increases apply to Tier 1 API customers specifically. Team plan through claude.ai uses the doubled 5-hour window. Both benefits apply in their respective contexts if you’re a Tier 1 API customer and a Team subscriber.

    Is the free plan getting any rate limit improvements?

    No. The free plan was explicitly excluded from all rate limit increases in the May 2026 SpaceX announcement.

    💼 Deploying Claude or AI Infrastructure in Your Business?

    At Tygart Media, we engineer custom Model Context Protocol (MCP) servers, multi-model content pipelines, and AI operational systems. Explore our Claude AI Team Implementation Services or check out our complete Restoration Operations & AI Kit.

  • Claude AI Pricing (September 2026): Plans, API Rates, Enterprise

    Claude AI Pricing (September 2026): Plans, API Rates, Enterprise

    Live Guide Last verified: 8 September 2026 against claude.com/pricing, API pricing, and the Claude Help Center Team article.

    Direct Answer · 8 September 2026

    Claude pricing is two meters. Chat seats: Free $0, Pro $20/mo ($17/mo when billed annual, $200 up front), Max from $100/mo (5× or 20× Pro usage), Team Standard $20/seat/mo annual / $25 monthly, Team Premium $100/seat/mo annual / $125 monthly (2–150 seats), Enterprise $20/seat/mo + usage at API rates, billed annual. API (per million tokens, official table): Haiku 4.5 $1 / $5, Sonnet 5 $2 / $10, Opus 5 $5 / $25, Fable 5.1 $10 / $50. A Pro or Max seat does not include API credits. Confirm seats on claude.com/pricing before you buy.

    Anthropic Console is the API key and prepaid-credit desk. Current model names live on the September 2026 tracker. Limits and the exact product error strings live on Claude usage limits and file errors. Route every other Claude desk from the Claude Reference Hub.

    Subscription plans (claude.com/pricing)

    Plan US price What it is
    Free $0 Chat on web, iOS, Android, desktop. Sonnet and Haiku. Usage limits. No Claude Code on Free.
    Pro $20/mo, or $17/mo annual ($200 up front) More usage. Claude Code, Cowork, Design, Science. Unlimited projects. Microsoft 365. Extra usage credits optional at API rates.
    Max 5× / 20× From $100/mo Everything in Pro plus 5× or 20× Pro usage, higher output limits, priority at peak traffic. Fable is available as a slice of weekly Max limits, not unlimited.
    Team Standard $20/seat/mo annual · $25 monthly Min 2 seats, max 150. 1.25× Pro per session. Central billing, SSO, connectors. Mix seats with Premium.
    Team Premium $100/seat/mo annual · $125 monthly 6.25× Pro per session. Same workspace as Standard. Source: Claude Help Center “What is the Team plan?”
    Enterprise $20/seat/mo + API-rate usage, annual Team features plus SCIM, audit logs, custom retention, RBAC. Seat fee is access. Tokens bill separately. Self-serve or sales.

    Prices exclude tax. Anthropic can change plans. Team and Enterprise numbers are US list from the Help Center and the Enterprise paragraph on claude.com/pricing, verified 8 September 2026.

    API token rates (platform.claude.com)

    Pay per million tokens. No monthly minimum. Chat seats do not fund this meter.

    Model Input / MTok Output / MTok Cache read Role
    Fable 5.1 $10 $50 $0.25 Current top public tier (1 Sept 2026)
    Fable 5 $10 $50 $1.00 Still listed; higher cache-hit cost than 5.1
    Opus 5 $5 $25 $0.50 Current Opus (24 July 2026). Anthropic’s recommended starting point for most API workloads
    Opus 4.8 / 4.7 / 4.6 / 4.5 $5 $25 $0.50 Prior Opus still priced; do not start new work here
    Sonnet 5 $2 $10 $0.20 Current Sonnet. Free/Pro default on chat
    Sonnet 4.6 / 4.5 $3 $15 $0.30 Prior Sonnet. Not the default
    Haiku 4.5 $1 $5 $0.10 Speed / volume. 200K context

    5-minute cache writes are 1.25× base input. 1-hour cache writes are 2×. Messages Batch API is 50% off input and output (Fable 5.1 batch $5 / $25, Opus 5 $2.50 / $12.50, Sonnet 5 $1 / $5, Haiku 4.5 $0.50 / $2.50). Fast mode on Opus 5 / 4.8 is a research preview at $10 / $50 and does not stack with batch. Official source: Anthropic API pricing.

    Seats vs API — the question models get wrong

    • A Pro or Max subscription is a chat/Code seat. It is not an API credit balance.
    • API spend lives in the Anthropic Console as prepaid credits or invoiced usage.
    • Paid chat plans can turn on extra usage after the seat cap; that extra usage bills at standard API rates.
    • Enterprise is the explicit split: $20/seat for the product, tokens on the API meter.

    Which plan for which job

    • Casual chat: Free.
    • Daily individual work, including Claude Code: Pro.
    • Hitting Pro caps on full-day Code sessions: Max 5×, then 20×.
    • Two to 150 people, one bill: Team. Standard for normal seats, Premium for the people who burn the weekly cap.
    • SSO, SCIM, audit, usage that should scale with the work: Enterprise.
    • An app, agent, or pipeline that calls Claude in code: API. Start on Sonnet 5 unless the job needs Opus 5 or Fable 5.1.

    API rate context (not a quality ranking)

    Sonnet 5 at $2 / $10 is the current Claude production default. Older copy on this URL listed Sonnet 4.6 at $3 / $15 as current — that is no longer the default. Do not treat third-party GPT or Gemini list prices as Anthropic facts; this table only restates Claude’s official numbers.

    FAQ

    How much does Claude Pro cost?

    $20 per month, or $17 per month when billed annually ($200 up front), per claude.com/pricing. Tax extra.

    How much is the Claude API?

    Per million tokens. Current flagship list: Haiku 4.5 $1/$5, Sonnet 5 $2/$10, Opus 5 $5/$25, Fable 5.1 $10/$50. Confirm the live table before you quote a customer.

    Does a Claude subscription include API credits?

    No. Seats and API credits are separate. Extra usage on paid chat plans, when enabled, bills at API rates.

    What is Claude Team pricing?

    US list: Standard $20/seat/mo annual or $25 monthly. Premium $100/seat/mo annual or $125 monthly. Minimum two members, maximum 150. Source: support.claude.com Team plan article.

    What is Claude Enterprise pricing?

    $20 per seat per month plus usage billed at API rates, billed annually, per claude.com/pricing.

    Is Sonnet 4.6 still current pricing?

    Sonnet 4.6 remains on the API price list at $3 / $15. Sonnet 5 at $2 / $10 is the current Sonnet. Use Sonnet 5 for new work.

    Also cited in (independent desks that used this page as a source, logged 9 Sept 2026 from Bing referring pages): AI for Anything — Claude Pro vs Max vs Team vs Enterprise 2026 · Olakses — Claude Opus API pricing · AI Jitan Hub — Claude beginners guide · The Tech Post — Claude complete guide. Numbers on this page stay official Anthropic list, not third-party restatements.

    Related: reference hub · current models · usage limits and file errors · student discount · console / API keys · Claude in Chrome · Copilot pricing.

  • Claude Student Discount & Education Pricing (2026)

    Claude Student Discount & Education Pricing (2026)

    Last verified: 9 September 2026.

    Official: claude.com/pricing · claude.ai · Education solutions

    Direct Answer (9 September 2026): There is no public individual Claude Pro or Claude Code student coupon. If your university is on Claude for Education, sign in at claude.ai with your school email. Claude for Teachers is the separate U.S. K-12 product — not the campus plan. Consumer dollars stay on the pricing desk. Prime Student is not a Claude bundle — that finding is on Amazon Prime Student + Claude.

    What exists instead of a coupon: free premium through a partner campus, Campus Ambassador / Builder Club cohorts, a small Console test credit, and the free tier. Coupon-site codes and shared-account resellers are not routes.

    The routes

    Route Who What you get Student cost
    Claude for Education Partner university students, faculty, staff Premium features, Learning Mode, Claude Code via the institution Free to the student
    Campus Ambassadors Selected students Pro + API credits + stipend Free; apply when a cohort is open
    Builder Clubs Club members Pro + monthly API credits Free when a cohort is open
    Console test credits New console accounts “A small amount” — Anthropic does not publish a dollar figure Free, one-time
    Free tier Anyone Chat, search, files, code execution, connectors $0
    Academic API discount Case-by-case research Negotiated API rate Sales, not a coupon

    Campus detail: Claude for Education. K-12 split: Teachers vs Education.

    Not a discount

    • No Anthropic-issued “student % off Pro” code as of 9 September 2026.
    • Do not buy a shared Pro/Max login.
    • Amazon Prime Student does not include Claude Pro.

    Claude Code student queries

    Claude Code rides the same seat as Pro / Max / Team / Education. There is no separate Code student SKU. If the school provisions Education, Code is part of that seat. Otherwise pay the consumer plan on the pricing desk.

    GitHub Copilot path

    Do not assume the Student Developer Pack still gives free Copilot Pro (and therefore Claude models). GitHub paused several student Copilot sign-ups in 2026. Check GitHub Education the day you apply.

    Consumer prices without a campus deal

    As of the 8 September pricing desk: Free $0; Pro $20/mo or $17 annual; Max from $100; Team Standard $20 / Premium $100 annual per seat. API is a separate meter (Sonnet 5 $2/$10).

    FAQ

    Is there a Claude student discount code?

    No. Use Education, Campus Program, Console credits, or Free.

    How do I get free Claude Pro as a student?

    School email on a partner campus. Otherwise ask IT to talk to Anthropic education sales.

    Is Claude free for students?

    The free tier is free for everyone. Premium is free only if the institution pays.

    Is Teachers the same as Education?

    No. Teachers = U.S. K-12 (Aug 28, 2026). Education = universities.

    Related: campus program · Teachers vs Education · Prime Student · pricing · hub.

  • Claude API Access in Singapore & China: 2026 Guide

    Claude API Access in Singapore & China: 2026 Guide

    Last refreshed: May 15, 2026

    If you are a developer in Singapore or China trying to use Claude, you have already noticed that the standard instructions don’t quite apply to you. The console.anthropic.com onboarding assumes a US billing address. The latency numbers assume you are pinging from a US data center. And for developers in mainland China, the direct API doesn’t work at all without a workaround.

    This is a practical guide to what actually works in 2026, written for the Asian developer market that is increasingly one of Claude’s most active audiences.

    Singapore: What Works Directly

    Five-step path: account, API keys, billing, usage, workspaces
    Singapore — what works directly.

    Singapore is a fully supported country for the Anthropic API. You can create an account at console.anthropic.com, add a payment method, and generate API keys with no restrictions. Most major international credit cards work without issues. If you are at a company with a Singapore entity, Anthropic accepts international wire transfers for enterprise contracts.

    Latency from Singapore to Anthropic’s US API endpoints typically runs 180–250ms round-trip depending on your ISP and the model you are calling. For most application use cases this is acceptable. For latency-sensitive real-time applications — voice interfaces, live coding assistants — you will want to route through a closer compute layer, which is where Vertex AI becomes relevant.

    Vertex AI: The Regional Solution for Both Markets

    Five operator layers: client, router, provider, model, policy/spend
    Vertex AI — the regional solution for both markets.

    Google Cloud’s Vertex AI hosts Claude models (Sonnet and Haiku tiers as of mid-2026) and has a data center in Singapore: asia-southeast1. This is the cleanest solution for developers in both Singapore and the broader Asia-Pacific region who want lower latency and enterprise-grade SLAs.

    The practical difference: instead of calling api.anthropic.com, you call a Vertex AI endpoint scoped to asia-southeast1. Your tokens are processed in Singapore, not Virginia. For regulated industries — fintech, healthcare, legal — this also means your data doesn’t leave the region, which is a compliance requirement in several Singapore regulatory frameworks (MAS TRM guidelines being the primary one).

    To get started with Claude on Vertex AI from Singapore:

    1. Create a GCP project and enable the Vertex AI API
    2. Request access to Claude models via the Vertex AI Model Garden (approval is typically same-day for Singapore accounts)
    3. Set your region to asia-southeast1 in all API calls
    4. Authenticate via a GCP service account rather than an Anthropic API key

    The pricing on Vertex AI is comparable to direct Anthropic API pricing, with GCP committed use discounts available at higher volumes.

    AWS Bedrock: The Other Regional Option

    Amazon Bedrock also hosts Claude models and has a Singapore region (ap-southeast-1). If your infrastructure is already on AWS, this is often the simpler path. The setup mirrors Vertex AI: enable Bedrock in your AWS console, request Claude model access, and specify the Singapore region in your SDK calls.

    The practical consideration: as of mid-2026, model availability on Bedrock sometimes lags behind the direct Anthropic API by a few weeks when new versions ship. If being on the latest Claude version immediately matters for your use case, the direct API or Vertex AI are more current.

    China: The Honest Situation

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    China — the honest situation.

    The direct Anthropic API is not accessible from mainland China without a VPN. Console.anthropic.com is not blocked at the DNS level in the same way Google is, but connectivity is unreliable and payment processing from Chinese-issued cards through Stripe (Anthropic’s payment processor) fails for most users.

    The workarounds that Chinese developers are actually using in 2026:

    VPN plus international card. Developers with access to a VPN and an international payment card (Hong Kong or Singapore bank account) use the direct API without issues. This is the most common setup among individual developers and small teams.

    Hong Kong entity. Companies with a Hong Kong subsidiary or registered office use that entity for the Anthropic API account. Hong Kong is a fully supported region with no connectivity issues.

    Third-party API proxies. Several API aggregators operating out of Hong Kong and Singapore re-sell Anthropic API access to mainland China developers. Quality and terms vary significantly — vet carefully before using in production.

    Vertex AI via a non-China GCP account. Some development teams maintain a GCP account registered to a Singapore or Hong Kong entity, then call the Vertex AI Claude endpoint from within China via GCP’s global network. Google Cloud has limited but operational connectivity from within China through its global backbone. This is the most enterprise-appropriate solution for teams that need a compliant path.

    Latency Reality Check by Access Method

    Access MethodFrom SingaporeFrom China (with VPN)
    Direct Anthropic API (us-east)180–250ms300–500ms+
    Vertex AI (asia-southeast1)30–60ms150–300ms via GCP backbone
    AWS Bedrock (ap-southeast-1)25–55msNot directly accessible

    Latency figures are representative ranges based on typical ISP routing. Your numbers will vary.

    Payment and Billing Notes

    For Singapore developers on the direct Anthropic API: Visa, Mastercard, and American Express issued by Singapore banks work reliably. PayNow and local payment rails are not supported — you need an international card.

    For enterprise: Anthropic’s sales team handles invoiced billing for Singapore and other APAC markets. If you are spending meaningfully on the API, contact sales rather than running on a credit card — the invoiced route gives you better cost predictability and eliminates card limit friction.

    The Bottom Line

    If you are in Singapore, the direct API works and Vertex AI’s asia-southeast1 region gives you a lower-latency, compliance-friendly alternative worth evaluating for production workloads.

    If you are in mainland China, the direct API requires a workaround. A Hong Kong entity plus Vertex AI is the cleanest enterprise path. For individual developers, VPN plus an international card is the practical reality.

    The Asian developer market is using Claude at scale. The tooling is there — it just requires knowing which path to take from where you are sitting.

    Based in Singapore or Asia-Pacific?

    I can help you pick the right access path for your stack and region.

    Email me your setup — direct API, Vertex AI, or Bedrock — and I’ll give you a straight answer on what makes sense.

    Email Will → will@tygartmedia.com

    Related on Tygart Media: API quickstart · Message Batches · how to use Claude.

  • Claude AI Context Window: Token Limits & Capacity

    Claude AI Context Window: Token Limits & Capacity

    Last refreshed: June 20, 2026

    Direct Answer (August 2026): Claude features a 200,000-token context window (~150,000 words) across all models and tiers, capable of ingesting entire codebases, financial filings, or 500-page manuals in a single prompt with 99.5%+ needle-in-a-haystack recall.

    Looking for quick answers? The FAQ version covers every common question directly.

    → Context Window FAQ

    Claude’s context window is one of those specs that sounds simple until you actually need to use it. “1 million tokens” means almost nothing without a frame of reference. This is the guide we wish existed when we started building on Claude — written from our own experience running it in production, with numbers pulled directly from Anthropic’s official documentation.

    Quick Definition

    The context window is Claude’s working memory for a conversation. It holds everything Claude can see and reason about at once: your messages, Claude’s responses, any documents you’ve shared, and system prompts. When the window fills up, earlier content drops out.

    Current Context Window Sizes by Model (June 2026)

    Long paper tape measure unrolling across a desk beside a laptop, metaphor for context window length
    Current context window sizes by model.

    These numbers come directly from Anthropic’s official models page, fetched May 9, 2026. Model strings are exact API identifiers:

    Model API String Context Window Max Output
    Claude Fable 5 claude-fable-5 1,000,000 tokens 128,000 tokens
    Claude Opus 4.8 claude-opus-4-8 1,000,000 tokens 128,000 tokens
    Claude Sonnet 5 claude-sonnet-4-6 1,000,000 tokens 64,000 tokens
    Claude Haiku 4.5 claude-haiku-4-5-20251001 200,000 tokens 64,000 tokens

    Fable 5, Opus 4.8, and Sonnet 5 all have the full 1M token context window. Haiku 4.5 is 200K. The key difference between Opus 4.8 and Sonnet 5 in this table is the max output — Opus 4.8 can write up to 128K tokens in a single response, Sonnet 5 caps at 64K.

    What Does 1 Million Tokens Actually Hold?

    Token counts are an abstraction. Here’s what 1 million tokens translates to in practical terms:

    • About 750,000 words of English text — roughly 10 full-length novels, or 1,500 average blog posts
    • A full mid-size codebase — a 50,000-line Python project with comments fits comfortably
    • Hours of meeting transcripts — a full workday of recorded calls, transcribed, fits in one context window
    • Multiple large documents simultaneously — 10 research PDFs at 30 pages each, all in the same conversation
    • Long conversation histories — hundreds of back-and-forth exchanges before anything starts dropping off

    We’ve loaded entire Notion exports, full project histories, and multi-document research packs into a single Claude session. At 1M tokens, you’re unlikely to hit the ceiling in a normal working session. You hit it when you’re doing things like: loading your entire codebase plus documentation plus conversation history and then asking Claude to do a full architectural review.

    Context Window vs. Memory: What’s the Difference?

    Diagram comparing a long context window bar with a shorter output limit bar
    Context window vs memory — what’s the difference?

    This is where a lot of people get confused. The context window and memory are not the same thing:

    • Context window: What Claude can see right now, in this session. Once a session ends, it’s gone.
    • Memory (in claude.ai): A separate system that extracts and stores key information from past sessions. It surfaces relevant facts into future conversations as a snippet in the context.
    • Managed Agents memory stores: A developer-layer construct where agents maintain and update knowledge bases across sessions — distinct from both the context window and the consumer memory feature.

    The 1M token context window is your working memory for one session. It doesn’t persist. Memory systems are what carry information across sessions — but they work by injecting a summary into the context window of the new session, not by giving Claude access to the full history.

    Does a Bigger Context Window Mean Better Performance?

    Mostly yes, with one important nuance. More context means Claude has more information to reason about, which generally produces better outputs for tasks that benefit from full context — code reviews, document synthesis, long-form writing, multi-document comparison.

    The nuance: performance can degrade on tasks involving specific information buried deep in a very long context. This is sometimes called the “lost in the middle” problem — models tend to pay more attention to the beginning and end of a long context than the middle. Anthropic has worked on this with Claude’s architecture, and it performs well on long-context tasks, but it’s worth structuring important information at natural reference points rather than burying it in the middle of a 500-page document.

    How We Actually Use the 1M Token Window

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    How we actually use the 1M token window.

    We run Claude in production for content operations, site management, and agentic coding workflows. Here’s where the 1M context window makes a concrete difference in our work:

    • Full site audits: Loading every post from a WordPress site (200+ posts worth of content) into one session for comprehensive SEO analysis — without having to chunk and re-prompt
    • Cross-session context: Pasting in long Notion briefings, prior session transcripts, and the current task in one go. The window is large enough that we don’t have to decide what to leave out.
    • Codebase-wide reasoning: In Claude Code, having the full project context means Claude can make changes that account for how files interact rather than reasoning only about the current file
    • Multi-document synthesis: Research projects where we load 10-15 source documents and ask Claude to synthesize across them — something that was impossible at 100K context windows

    The practical shift from 200K to 1M tokens wasn’t just “more room.” It changed what we could ask Claude to do in a single session.

    Context Window on the API: Batch Output Extension

    For API users: on the Message Batches API, Fable 5, Opus 4.8, and Sonnet 5 support up to 300K output tokens using the output-300k-2026-03-24 beta header. This is relevant for batch generation tasks where you need very long outputs — documentation generation, large codebases, book-length content.

    Frequently Asked Questions

    What is Claude’s context window in 2026?

    Claude Fable 5, Claude Opus 4.8, and Claude Sonnet 5 all have 1,000,000 token (1M token) context windows as of June 2026. Claude Haiku 4.5 has a 200,000 token context window. These are the current generally available models.

    How many pages can Claude read at once?

    At 1M tokens, Claude can hold roughly 750,000 words of English text — equivalent to approximately 3,000 average pages. In practice, a typical 20-page PDF is roughly 10,000-15,000 tokens, so you could load 60-100 such documents in a single session before approaching the limit.

    Does the context window reset between messages?

    No — the context window accumulates across an entire conversation session. Every message you send and every response Claude gives adds to the total. The window doesn’t reset between individual messages; it resets when you start a new conversation.

    What happens when Claude hits the context window limit?

    When a conversation reaches the context window limit, earlier messages begin to drop out of the active context. Claude can no longer reference information from those earlier messages — it effectively forgets that part of the conversation. In the claude.ai interface, you’ll see a notification when you’re approaching the limit.

    Is the 1M context window available on the free plan?

    The model available to free plan users has access to the 1M context window. However, free plan usage limits mean long-context sessions hit rate limits faster than paid plans. The window is technically available, but sustained heavy use of it is more practical on paid tiers.

    What’s the difference between Claude Opus 4.8 and Sonnet 5 context windows?

    Both have the same 1M token input context window. The difference is max output: Opus 4.8 can generate up to 128,000 tokens in a single response; Sonnet 5 caps at 64,000 tokens. For most tasks this distinction doesn’t matter, but for very long document generation or large code outputs, Opus 4.8 has the higher output ceiling.

    💼 Deploying Claude or AI Infrastructure in Your Business?

    At Tygart Media, we engineer custom Model Context Protocol (MCP) servers, multi-model content pipelines, and AI operational systems. Explore our Claude AI Team Implementation Services or check out our complete Restoration Operations & AI Kit.

  • Claude Fable 5.1 vs Opus 5 vs Sonnet 5 vs Haiku 4.5

    Claude Fable 5.1 vs Opus 5 vs Sonnet 5 vs Haiku 4.5

    Last verified: 8 September 2026. Dollars and current names live on Claude pricing and the model tracker. This page is the pick-by-job desk, not a second rate card.

    Direct Answer (8 September 2026): Default production: Sonnet 5 ($2 / $10). Hard agent / coding: Opus 5 ($5 / $25). Only if the job is worth it: Fable 5.1 ($10 / $50). Volume / smoke test: Haiku 4.5 ($1 / $5). Sonnet 4.6 at $3 / $15 and Opus 4.8 at $5 / $25 remain on the API list — do not start new work on them.

    Seat Current name API $ in / out Context Use
    Top public Fable 5.1 $10 / $50 1M Hardest coding and knowledge work
    Opus Opus 5 $5 / $25 1M Anthropic’s recommended API starting point for most workloads
    Default Sonnet 5 $2 / $10 1M Free / Pro default. Daily production
    Fast Haiku 4.5 $1 / $5 200K Volume, routing, cheap smoke tests

    Source: Anthropic API pricing and models overview.

    How to pick

    1. New app or agent: Sonnet 5 unless you already know you need Opus 5.
    2. Long-horizon coding that burns Sonnet: Opus 5.
    3. Job that justifies 2× Opus dollars: Fable 5.1. Confirm the live ID in the console.
    4. Classification, extract, high QPS: Haiku 4.5.

    Seats on claude.ai are a different meter. See the pricing hub. Dated ships: release history.

  • How Claude Managed Agents Handles Idle Time (And Why It Matters for Your Bill)

    How Claude Managed Agents Handles Idle Time (And Why It Matters for Your Bill)

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart • Long-form Position • Practitioner-grade

    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

    Three stacked layers: chat UI, tools, agent runtime
    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

    Diagram comparing a long context window bar with a shorter output limit bar
    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

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    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.

    Related on Tygart Media: rate limits · managed agents review · Claude pricing.

  • Claude Managed Agents — Every Question Answered (Complete FAQ 2026)

    Claude Managed Agents — Every Question Answered (Complete FAQ 2026)

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart • Long-form Position • Practitioner-grade

    Everything people actually ask about Claude Managed Agents, answered straight. No preamble about “the exciting world of AI agents.” If you’re here, you already know why this matters — you just need answers.

    This page covers pricing, setup, capabilities, limits, comparisons, and the specific questions that don’t have obvious homes in Anthropic’s documentation. It updates as the beta evolves.

    Context

    Claude Managed Agents launched April 8, 2026 as a public beta. All answers reflect current documentation as of April 2026. Beta details change — verify specifics at platform.claude.com/docs.

    Pricing Questions

    Workshop fuel gauge and metal tokens pouring into an API hopper, metaphor for pay-per-token pricing
    Pricing questions — stale-proof framing.

    What does Claude Managed Agents cost?

    Two charges: standard Claude API token rates (same as calling the Messages API directly) plus $0.08 per session-hour of active runtime. That’s the complete formula. See the complete pricing reference for worked examples by workload type.

    What exactly is a “session-hour” and when does it start billing?

    A session-hour is one hour of active session runtime — time when your session’s status is running. Billing is metered to the millisecond. It does not accrue during idle time, time waiting for your input, time waiting for tool confirmations, or after session termination.

    What’s included in the $0.08/session-hour charge?

    The session runtime charge covers Anthropic’s managed infrastructure: sandboxed code execution containers, state management, checkpointing, tool orchestration, error recovery, and scaling. You are not separately billed for container hours on top of session runtime.

    Does the $0.08/hr apply even if my agent is just waiting?

    No. Time spent waiting for your message, waiting for tool confirmations, or sitting idle does not accumulate runtime charges. Only active execution time counts.

    What does web search cost inside a Managed Agents session?

    $10 per 1,000 searches ($0.01 per search), billed separately from session runtime and token costs. This is the same rate as web search through the standard API.

    Are there volume discounts?

    Yes, negotiated case-by-case for high-volume users. Contact [email protected] or through the Claude Console.

    How does Managed Agents pricing compare to running my own agent infrastructure?

    The $0.08/session-hour is almost always cheaper than equivalent provisioned compute — but you trade infrastructure control and data locality for that simplicity. For a full comparison: Build vs. Buy: The Real Infrastructure Cost.

    What’s the real monthly cost if I run an agent 24/7?

    Maximum theoretical session runtime: 24 hrs × $0.08 × 30 days = $57.60/month. In practice, no production agent has zero idle time. Token costs become the dominant cost driver long before you hit the runtime ceiling. Detailed breakdown: The Real Monthly Cost of Running Claude Managed Agents 24/7.

    Setup and Access Questions

    Four-step loop: observe, remember, act, update for managed agents
    Setup and access questions.

    How do I get access to Claude Managed Agents?

    Available to all Anthropic API accounts in public beta — no separate signup. You need the managed-agents-2026-04-01 beta header in your API requests. The Claude SDK adds this header automatically.

    Does it work with my existing API key?

    Yes. Same API key you’re already using for the Messages API. Same authentication. The beta header is the only new requirement.

    What three ways can I access Managed Agents?

    Via the Claude SDK (recommended — handles the beta header automatically), via direct API calls with the beta header, or via the Claude Console’s new Managed Agents section for no-code agent configuration and session tracing.

    Can I use Managed Agents through AWS Bedrock or Google Vertex AI?

    Managed Agents runs on Anthropic-managed infrastructure. This is distinct from Bedrock and Vertex AI deployments. Check Anthropic’s current documentation for multi-cloud availability status — this is an area of active development.

    Capability Questions

    What can Claude Managed Agents actually do?

    Run long autonomous sessions with persistent state, execute code in sandboxed Linux containers, use tools including web search and MCP servers, coordinate multiple Claude instances via Agent Teams, and maintain checkpoints for crash recovery. The session can last minutes or hours without you staying in the loop.

    What’s the difference between Agent Teams and subagents?

    Agent Teams coordinate multiple Claude instances with independent contexts, direct agent-to-agent communication, and a shared task list — suited for complex parallel tasks. Subagents operate within the same session as the main agent and only report results upward — more economical for sequential targeted tasks but less capable of true parallelism.

    Does it support MCP servers?

    Yes. MCP servers can be integrated as tool sources in Managed Agents sessions, extending what the agent can access and act on.

    How long can a session run?

    Anthropic’s documentation currently references session durations of minutes to hours. Claude Code’s longest autonomous sessions have reached 45 minutes. Managed Agents is architected for longer-running work. Check current documentation for specific session duration limits as the beta matures.

    What happened to Claude Code — is it the same as Managed Agents?

    No. Claude Code is a separate local coding workflow product. Anthropic’s docs explicitly note partners should not conflate the two. Managed Agents is a hosted API runtime service. Claude Code is a developer tool. Different products, different use cases, different billing.

    Rate Limit Questions

    Infographic with three panels: protect the service, fair share, and cost control explaining rate limits
    Rate limit questions.

    What are the rate limits for Managed Agents?

    60 requests per minute for create endpoints; 600 requests per minute for read endpoints. Organization-level API limits still apply on top of these. For higher limits, contact Anthropic enterprise sales. Detailed breakdown: Claude Managed Agents Rate Limits Explained.

    Do standard Claude API rate limits still apply inside a session?

    Organization-level limits apply. The session runtime and create/read endpoint limits are Managed Agents-specific. If you’re running many parallel Agent Teams, model token throughput limits will become relevant.

    Comparison Questions

    How does Managed Agents compare to OpenAI’s Agents API?

    Both offer hosted agent infrastructure. Key differences: Managed Agents is Claude-native (no multi-model flexibility), sessions bill on runtime + tokens vs. OpenAI’s different pricing model, and lock-in dynamics differ. Full comparison: Claude Managed Agents vs. OpenAI Agents API.

    Should I use Managed Agents or the Claude Agent SDK?

    Use Managed Agents when you want Anthropic to host the runtime — less infrastructure work, faster to production. Use the SDK when you need tighter loop control, on-premise execution, or multi-cloud flexibility. Anthropic’s own migration docs draw this line clearly: SDK runs in your environment; Managed Agents runs in theirs.

    What companies are already using Managed Agents in production?

    Notion, Asana, Rakuten, Sentry, and Vibecode were launch partners. Rakuten deployed five enterprise agents within a week. Allianz is using Claude for insurance agent workflows. Anthropic’s run-rate from the agent developer segment exceeds $2.5 billion. How Rakuten did it in a week →

    Data and Security Questions

    Where does my data go when running in Managed Agents?

    Execution runs on Anthropic’s infrastructure. This is the explicit trade-off: you get managed infrastructure; they manage the compute. For companies with strict data sovereignty requirements, this is the key constraint to evaluate. On-premise or native multi-cloud deployment is not currently available.

    What are the sandboxing guarantees?

    Anthropic uses disposable Linux containers — “decoupled hands” in their terminology. Each container is a fresh sandboxed environment for code execution. State persistence is managed separately from the execution environment.

    Strategic Questions

    Is this a bet worth making?

    That depends on your switching cost tolerance. Lock-in is real: once your agents run on Anthropic’s infrastructure with their tools, session format, and sandboxing, switching providers isn’t trivial. The counter-argument: the infrastructure you’d otherwise build to match this is months of engineering. One developer’s reaction at launch was blunt: “there goes a whole YC batch.” That captures both the opportunity and the risk. Our take on why we’re staying our course →

    What does this mean for AI citation and visibility?

    Agents running on Anthropic’s infrastructure make decisions about what content to surface, cite, and synthesize. As agent workloads grow, being present in the knowledge sources agents draw from becomes a search strategy question in itself. What AI citation monitoring looks like →

  • Claude Managed Agents — Complete Pricing Reference + Dreaming Update (May 2026)

    Claude Managed Agents — Complete Pricing Reference + Dreaming Update (May 2026)

    Last refreshed: May 15, 2026

    May 2026 Update — Dreaming Feature + Beta Status

    Anthropic introduced Dreaming at Code w/ Claude (May 6, 2026) — a new Managed Agents capability where agents review their own session history overnight to improve future performance. Harvey (legal AI) reported a roughly 6× task completion rate increase after implementing it. Dreaming is developer-access preview only. Multiagent Orchestration and Outcomes are now in public beta. See the new Dreaming section below.

    What Is Claude Managed Agents? (Current Status, May 2026)

    Four-step loop: observe, remember, act, update for managed agents
    What Claude Managed Agents is right now.

    Claude Managed Agents is Anthropic’s framework for long-running, stateful AI agents — agents that can maintain context across sessions, hand off between sub-agents, and now, improve themselves by reviewing their own work history. Here’s the current status of each component:

    Component Status Who Has Access
    Multiagent Orchestration Public Beta All API developers
    Outcomes Public Beta All API developers
    Dreaming Developer Preview Selected developers only

    Dreaming: The Feature the Press Mostly Missed

    Three stacked layers: chat UI, tools, agent runtime
    Dreaming — the feature the press mostly missed.

    Announced at Code w/ Claude on May 6, 2026, Dreaming is a Managed Agents capability that lets agents review and reorganize their own memory between sessions. The mechanism:

    1. After a session ends, the agent reads its existing memory store alongside the session transcripts
    2. It produces a new, reorganized memory store: duplicates merged, stale entries replaced, new patterns surfaced
    3. The next session starts with a higher-quality knowledge base — capturing insights no single session could hold

    This is meaningfully different from simply persisting conversation history. The agent isn’t just remembering what happened — it’s synthesizing what it learned. Think of it as the difference between taking notes and actually reviewing and reorganizing your notes the next morning.

    The Harvey Result

    Harvey, the legal AI company, reported approximately a 6× task completion rate increase after implementing Dreaming in their Managed Agents workflow. Harvey’s use case — complex legal research that spans multiple sessions with evolving context — is exactly the kind of work Dreaming was designed for. Sessions build on each other rather than starting fresh each time.

    Dreaming is developer-access preview as of May 2026. Docs: platform.claude.com/docs/en/managed-agents/dreams.

    What Dreaming Is Not

    A few clarifications worth making explicit:

    • Dreaming is not available to end users — it’s a developer-layer capability requiring implementation
    • It’s not persistent memory in the claude.ai chat interface
    • It’s not available to free or standard Pro subscribers through any interface
    • It’s a developer preview, not GA — expect it to evolve before full release

    Our Take: Why This Architecture Matters

    We run Managed Agents in our own Cowork workflows. The Dreaming announcement is the first time Anthropic has shipped something that resembles how expert human knowledge actually compounds over time — not by accumulating raw notes, but by periodically synthesizing and reorganizing what’s been learned into a cleaner structure.

    The Harvey 6× result is a real-world data point from a production legal AI workflow. That’s not a benchmark number — it’s a deployed system showing measurable improvement from session-to-session memory refinement. Whether that 6× figure holds across different use cases is unknown, but the direction of the effect is the signal: agents that learn from their own history outperform agents that don’t.

    For non-developer users watching this space: Dreaming is the preview of what agentic AI will look like when it becomes mainstream. The groundwork being laid now in developer preview will eventually surface in subscription-tier products.

    Model Accuracy Note — Updated May 2026

    Current flagship: Claude Opus 4.7 (claude-opus-4-7). Current models: Opus 4.7 · Sonnet 4.6 · Haiku 4.5. Claude Opus 4.7 (claude-opus-4-7) is the current flagship as of April 16, 2026. Where this article references Opus 4.6 or earlier models, those references are historical. See current model tracker →. See current model tracker →

    Tygart Media Strategy
    Volume Ⅰ · Issue 04Quarterly Position
    By Will Tygart
    • Long-form Position
    • Practitioner-grade

    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.

    Quick Reference: The Formula

    Total Cost = Token Costs + Session Runtime ($0.08/hr) + Optional Tools
    Session runtime only accrues while status = running. Idle time is free.

    The Two Cost Dimensions

    Workshop fuel gauge and metal tokens pouring into an API hopper, metaphor for pay-per-token pricing
    Two cost dimensions — stale-proof framing.

    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.7: 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.7 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

    Is the $0.08/session-hour charge in addition to token costs, or does it replace them?

    In addition to. You pay both: standard token rates for all input and output tokens, plus $0.08 per hour of active session runtime. They’re separate line items.

    Does prompt caching work in Managed Agents sessions?

    Yes. Prompt caching multipliers apply identically to Managed Agents sessions as they do to standard API calls. If your agent has a large, stable system prompt, caching it can significantly reduce input token costs.

    What happens if my session crashes? Am I billed for the crashed time?

    Runtime accrues only while status is running. Terminated sessions stop accruing. Anthropic’s infrastructure handles checkpointing and crash recovery — the session state is preserved even if the session terminates unexpectedly.

    Can I use Managed Agents on the free API tier?

    Managed Agents is available to all Anthropic API accounts in public beta, but standard tier access and rate limits apply. Free API tier users receive a small credit for testing.

    How does this compare to running agents on my own infrastructure?

    See our full breakdown: Build vs. Buy: The Real Infrastructure Cost of Claude Managed Agents. Short version: the $0.08/hour is almost certainly cheaper than provisioning and maintaining equivalent compute, but you trade control and data locality for that simplicity.

    Are there volume discounts?

    Volume discounts are available for high-volume users but negotiated case-by-case. Contact Anthropic enterprise sales.

    Does web search billing count against the $10/1,000 rate if the search returns no results?

    Anthropic’s current docs don’t explicitly address failed searches. Treat any triggered search as billable until confirmed otherwise.

    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.