Tag: Claude AI

  • Claude Code Billing & Monthly Credit Pools (2026)

    Claude Code Billing & Monthly Credit Pools (2026)

    Last verified: October 5, 2026 (Pacific)

    Claude Code has two billing models, and which one applies depends on how you run it, not just which plan you hold. When you use Claude Code interactively in the terminal or IDE on a Pro or Max plan, it draws from the same subscription usage limits as your Claude.ai chats. But starting June 15, 2026, Anthropic separates out programmatic usage: the Claude Agent SDK, the claude -p headless command, the Claude Code GitHub Actions integration, and third-party apps that authenticate through the Agent SDK will no longer count against your interactive subscription pool. Instead they draw from a new, separate monthly Agent SDK credit, billed at standard API rates. This page documents both models, the exact credit amounts per plan, and the SDK package rename you may also need to handle.

    The two billing models at a glance

    Workshop fuel gauge and metal tokens pouring into an API hopper, metaphor for pay-per-token pricing
    Two billing models at a glance — no sticky dollar stickers.

    The dividing line is interactive vs. programmatic. One number to remember: setting an ANTHROPIC_API_KEY environment variable overrides your subscription entirely — Claude Code then authenticates with that key and bills as pay-as-you-go API usage, regardless of plan.

    Usage type How it runs Billed against
    Interactive Claude Code Terminal or IDE, human at the keyboard Pro/Max subscription usage limits
    Claude.ai chat Web, desktop, mobile Pro/Max subscription usage limits
    Agent SDK (Python/TypeScript) Your own programmatic projects Separate Agent SDK credit (from June 15, 2026)
    claude -p (non-interactive) Headless / scripted Claude Code Separate Agent SDK credit (from June 15, 2026)
    Claude Code GitHub Actions CI/CD automation Separate Agent SDK credit (from June 15, 2026)
    Any usage with ANTHROPIC_API_KEY set API-key auth instead of subscription Standard API rates (pay-as-you-go)

    What changes on June 15, 2026

    Per Anthropic’s support documentation: “Starting June 15, 2026, Claude Agent SDK and claude -p usage no longer counts toward your Claude plan’s usage limits.” Each subscription tier instead receives a fixed monthly Agent SDK credit. When that credit runs out, additional Agent SDK usage flows to usage credits at standard API rates — but only if you have enabled usage credits. If you have not, “Agent SDK requests stop until your credit refreshes.” Unused credits do not roll over to the next billing cycle, and there is no automatic fallback to the interactive pool.

    Plan Monthly Agent SDK credit
    Pro $20
    Max 5x $100
    Max 20x $200
    Team (Standard seats) $20
    Team (Premium seats) $100
    Enterprise (seat-based Premium) $200

    What stays on the interactive subscription pool, unchanged: Claude conversations on web, desktop, and mobile; and interactive Claude Code in the terminal or IDE. The change is scoped strictly to programmatic execution.

    How each pool is metered and priced

    Infographic with three panels: protect the service, fair share, and cost control explaining rate limits
    How each pool is metered.

    Claude Code “charges by API token consumption” — the underlying meter is input/output tokens, including thinking tokens billed as output. On a subscription, that token consumption is what counts against your plan limits (interactive) or your Agent SDK credit (programmatic). The Agent SDK credit and any overflow are billed at standard API list rates; the per-model API token prices below are the verified current rates.

    Pool Meter Price basis
    Interactive (Pro/Max) Tokens, against plan usage limits Included in subscription
    Agent SDK credit Tokens, against monthly credit Standard API rates
    Overflow past the credit Tokens, usage credits Standard API rates (only if usage credits enabled)
    API key (ANTHROPIC_API_KEY) Tokens, pay-as-you-go Standard API rates

    Verified current API token prices (per million tokens) for models commonly used in Claude Code:

    Model Model ID Input $/Mtok Output $/Mtok
    Claude Sonnet 5.5 claude-sonnet-5-5 $2.00 $10.00
    Claude Opus 5.5 claude-opus-5-5 $4.00 $20.00
    Claude Fable 5.1 claude-fable-5-1 $10.00 $50.00
    Claude Opus 4.8 (legacy — still listed) claude-opus-4-8 $5.00 $25.00
    Claude Sonnet 4.6 (legacy — still listed) claude-sonnet-4-6 $3.00 $15.00
    Claude Haiku 4.5 claude-haiku-4-5 $1.00 $5.00

    Subscription plan prices

    These are the published Claude plan prices the Agent SDK credits attach to. The Max 5x plan starts at $100/month; the $200 figure for Max 20x is documented as the matching Agent SDK credit amount for that tier.

    Plan Price
    Free $0
    Pro $20/month, or $17/month billed annually ($200 up front)
    Max 5x From $100/month
    Team (Standard seat) $25/seat/month, or $20/seat/month billed annually

    The SDK rename: claude-code-sdk to claude-agent-sdk

    Separate from billing, the SDK itself was renamed. Anthropic’s migration guide states: “The Claude Code SDK has been renamed to the Claude Agent SDK.” If you have code on the old package, you must update the package name, imports, and one Python type. The headless CLI command name is unchanged — it is still claude -p.

    Aspect Old New
    npm package (TS/JS) @anthropic-ai/claude-code @anthropic-ai/claude-agent-sdk
    Python package claude-code-sdk claude-agent-sdk
    Python options type ClaudeCodeOptions ClaudeAgentOptions
    Default system prompt Claude Code’s preset Minimal (opt back in via preset: "claude_code") 
    # TypeScript
npm uninstall @anthropic-ai/claude-code
npm install @anthropic-ai/claude-agent-sdk

# Python
pip uninstall claude-code-sdk
pip install claude-agent-sdk

    Decision: which billing path applies to your work

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    Which billing path applies to your work.
    If you are… Billing path
    A developer coding interactively in the terminal Subscription usage limits (unchanged)
    Running claude -p in a script or cron job Agent SDK credit (from June 15, 2026)
    Running Claude Code in GitHub Actions Agent SDK credit (from June 15, 2026)
    Building an app on the Agent SDK with subscription auth Agent SDK credit (from June 15, 2026)
    A team or service account wanting budgets + usage reports Set ANTHROPIC_API_KEY → standard API billing

    Does interactive Claude Code billing change on June 15, 2026?

    No. Anthropic’s documentation confirms interactive Claude Code in the terminal or IDE, and Claude conversations on web, desktop, and mobile, continue using subscription usage limits as before. Only programmatic usage — the Agent SDK, claude -p, GitHub Actions, and third-party Agent SDK apps — moves to the separate Agent SDK credit.

    How much is the separate Agent SDK credit?

    $20/month on Pro, $100 on Max 5x, $200 on Max 20x, $20 on Team Standard seats, $100 on Team Premium seats, and $200 on Enterprise seat-based Premium. The credit is billed at standard API rates, does not roll over, and refreshes monthly.

    What happens when the Agent SDK credit runs out?

    Additional Agent SDK usage flows to usage credits at standard API rates — but only if you have enabled usage credits. If you have not enabled them, Agent SDK requests stop until your credit refreshes. There is no automatic fallback to your interactive subscription pool.

    How do I avoid the credit pool entirely?

    Set an ANTHROPIC_API_KEY environment variable. Claude Code and the Agent SDK then authenticate with that key and bill as standard pay-as-you-go API usage, separate from any subscription. This is Anthropic’s recommended path for apps, CI jobs, service accounts, and team-owned projects that need budgets and usage reporting.

    Was the Claude Code SDK renamed?

    Yes. It is now the Claude Agent SDK. The npm package @anthropic-ai/claude-code became @anthropic-ai/claude-agent-sdk, the Python package claude-code-sdk became claude-agent-sdk, and the Python type ClaudeCodeOptions became ClaudeAgentOptions. The claude -p CLI command name is unchanged.

    Related on Tygart Media: Claude Code getting started · Claude pricing · Pro vs Max.


    Part of the complete guide: Claude Code

  • I Actually Used Claude Fable 5 Before the Government Pu (2026)

    I Actually Used Claude Fable 5 Before the Government Pu (2026)

    Three days. That’s how long Claude Fable 5 existed in the wild before the US government killed it.

    On Monday, June 9, Anthropic launched Fable 5 and Mythos 5. On Thursday, June 12, Commerce Secretary Howard Lutnick issued an export control directive ordering Anthropic to suspend access for any foreign national. Since Anthropic can’t verify nationality in real time, they shut it down for everyone. Globally. Immediately. The stated reason was a narrow jailbreak vulnerability — one Anthropic says exists in other publicly deployed models too.

    I’m not writing this to debate export controls. I’m writing this because I spent those three days running Fable 5 in production — not benchmarking it, not kicking the tires, actually building with it — and I have something most people writing about this don’t have: receipts.

    Day One: The Model Dropped and I Put It to Work

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    Day one — the model dropped and I put it to work.

    Fable 5 launched June 9. By that afternoon, I had it running a Batch 8 sprint across my Tygart Media site — refreshing 10 pages of Claude content that needed updating. Fable 5 updated comparison tables, corrected model names across the lineup, added FAQPage schema, injected internal links, and expanded word counts. Post 4787 went from 750 words to 1,602. Post 9821 went from 1,782 to 2,543. Five posts refreshed with full SEO treatment — schema, FAQs, RankMath meta, silo links — in a single session.

    That same day, I had Fable 5 write a complete guide to itself. Not a press release rewrite — a 2,100-word article with an interactive cost calculator, a model picker tool, and a section called “How We Actually Use Each Model” that mapped my real production workflows to each tier: Haiku for the daily 25-post SEO sweeps, Sonnet for desk articles, Opus for deep refreshes, Fable for portfolio-wide audits and strategy. The draft landed in Notion with scoped CSS and JS, ready to paste into WordPress as a single Custom HTML block.

    Day Two: Fable 5 Ran My Entire SEO Audit

    GEO versus SEO comparison cards
    Day two — Fable 5 ran the SEO audit.

    June 10. I ran a full SEO audit of tygartmedia.com through Fable 5. It identified that Fable 5 itself was the top content gap — a model launched 24 hours ago with zero dedicated coverage and peak search intent. So it wrote the article to fill its own gap. It drafted the piece, tagged the slug, assigned the category, and queued internal links to five existing posts.

    That same day, Fable 5 wrote and published “The Signal: AI Just Split Into Two Lanes” — a 1,400-word field notes piece that wove together Fable 5’s launch, OpenAI’s S-1, Chrome WebMCP, and the emerging thesis that AI was splitting into a product lane and an infrastructure lane. The article went through the full pipeline: SEO optimization, AEO with 8 FAQ Q&As, GEO entity enrichment, Article + FAQPage schema, taxonomy assignment, internal linking, quality gate — then published via REST API. It even created the LinkedIn draft in Metricool and scheduled it for 2:30 PM Pacific.

    That article exists right now at tygartmedia.com. I didn’t write it. Fable 5 did, with me directing the strategy and approving the output. The quality bar was real journalism, not AI slop.

    Day Three: Building the Infrastructure Layer

    June 11. While the Fable 5 Complete Guide sat in Notion waiting for a featured image, I was using Fable 5 to build the systems that would keep my content operation running. I had it update the Claude Intelligence Desk — my Notion page that serves as the authoritative source of truth for every Claude model name, API string, and price across my entire content operation. Every article gets verified against that desk before publishing. Fable 5 updated it with its own pricing: $10 input, $50 output per million tokens.

    I also had Fable 5 design my Pricing Freshness Engine — a WordPress mu-plugin that shadow-checks Anthropic’s live pricing against what’s displayed on my site. The engine had been running in shadow mode since June 2, catching drift before it reaches readers. Fable 5 added itself to the canonical pricing store.

    Meanwhile, my 6 scheduled email agent tasks — morning triage, midday check, afternoon wrap, newsletter extraction, weekly prep, and weekly self-audit — were running on the same Claude infrastructure, handling my inbox while I focused on building. The whole system runs on my Max plan. No extra API charges.

    What Fable 5 Actually Felt Like

    Here’s what the benchmarks don’t tell you: Fable 5 understood intent, not just instructions.

    When I told it to run a page refresh, it didn’t just update the text — it checked model names against my Intelligence Desk, verified pricing against live documentation, added schema markup, expanded FAQs, injected internal links, and updated the dateline. It treated each task as a system, not a checklist.

    When I asked it to write the Complete Guide, it included a section about how we actually use each model tier in production — because it knew from context that an article about Claude models on a site that runs on Claude models should demonstrate firsthand expertise, not just recite specs. It even built interactive JavaScript widgets inline — a cost calculator and a model picker — without being asked, because it understood the article needed to be useful, not just informative.

    The gap between Fable 5 and what came before it was the largest single-model jump I’ve experienced since I started building on Claude in 2024.

    What Most Commentators Are Missing

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    What most commentators are missing.

    Most people writing about the shutdown never used Fable 5. They’re debating precedent, policy, the implications for AI regulation. All valid. But the conversation is incomplete without understanding what was actually deployed.

    This is the first time the US government has aimed export controls at a deployed commercial AI model rather than at chips or hardware. That’s unprecedented. Anthropic complied but publicly disagreed, calling it a likely misunderstanding based on a narrow jailbreak that exists in other models too.

    Every other Claude model — Opus, Sonnet, Haiku — remains fully available and unaffected.

    What I Lost

    Here’s what the government took from me specifically:

    My Fable 5 Complete Guide is sitting in Notion, ready to publish, with the proxy fix queued. The pricing pages need Fable 5 rows added. The Freshness Engine needs Fable 5 in its canonical store. The WordPress proxy’s ALLOWED_DOMAINS needs a one-line gcloud update. All of it was queued up. All of it was dependent on a model that no longer exists.

    The infrastructure I built this week — the Intelligence Desk, the Pricing Freshness Engine, the content pipeline that ran “The Signal” from draft to published with schema and social scheduling in a single session — all of that still works with Opus and Sonnet. But the ceiling is lower. The tasks that Fable 5 handled in one pass will take two or three with the models that remain.

    What Happens Now

    Anthropic says this isn’t permanent. They’re working to restore access.

    For people like me who build businesses on top of these tools, the uncertainty is the real cost. Three days is long enough to build production workflows, deploy infrastructure, and write articles that reference a model’s existence — and short enough that all of it gets yanked before you can publish.

    But I’m not pulling back. This week confirmed the trajectory. AI at this level isn’t a nice-to-have — it’s the infrastructure of how modern knowledge work gets done. Whether it’s Fable 5 or whatever comes after it, this capability exists now. You can’t un-ring that bell.

    I know because I rang it. For three days, I built real things with a model the government decided the world shouldn’t have. And the work is still there in my Notion, waiting.

    Will Tygart is the founder of Tygart Media, where he builds AI-native content operations across a portfolio of WordPress sites. He has been building production workflows on Claude since 2024. His Claude Intelligence Desk, Pricing Freshness Engine, and content pipeline systems were all built or upgraded using Claude Fable 5 during its three-day window.

    Related on Tygart Media: Fable 5 complete guide · Claude Fable 5 · how to use Claude.

  • Latest Claude Models — moved to the tracker

    Latest Claude Models — moved to the tracker

    This slug duplicates the ranking tracker. Numbers here were last written as June 2026.

    Direct Answer (9 September 2026): Claude 3.5 Sonnet is retired. Current public Sonnet is Sonnet 5 at $2 / $10 per MTok. Current lineup is Fable 5.1, Opus 5.5 ($4 / $20 per MTok), Opus 5, Sonnet 5, Haiku 4.5. Live tracker: current Claude model version. Seat dollars: pricing hub.

    Do not ship 3.5 Sonnet, Sonnet 4.6, or Opus 4.8 IDs in new work. Confirm the alias in the console.

  • What Is Model Context Protocol (MCP)? The Complete Guid (2026)

    What Is Model Context Protocol (MCP)? The Complete Guid (2026)

    Model Context Protocol (MCP) is the reason Claude can read your files, query your database, search the web, and push code to GitHub — all from inside a single conversation. Without it, Claude would be limited to whatever you paste in manually. With it, Claude connects to almost any external system.

    Quick answer: MCP is an open standard developed by Anthropic that lets AI models securely connect to external tools, data sources, and services through a standard client-server architecture. You install an MCP server for the system you want Claude to access. Claude becomes a client that calls that server. The server executes the action and returns results.

    The Problem MCP Solves

    Flow from app/IDE through MCP to servers and data APIs
    The problem MCP solves: one protocol, many tools.

    Before MCP, connecting an AI model to external data meant one of two things: either the AI company built a native integration (slow, expensive, proprietary), or you cobbled together a pipeline that passed data manually between systems.

    Neither approach scales. If Claude natively supported every database, every API, every file format, and every SaaS tool on the planet, the model would be perpetually behind. And manual copy-paste workflows aren’t agentic — they require you to do all the coordination work the AI should be doing.

    MCP solves this with a universal adapter layer. Instead of building individual integrations, Anthropic defined a standard. Now any developer can build an MCP server for any system, and any MCP-compatible AI client (like Claude) can use it automatically.

    How MCP Works

    Three stacked layers: chat UI, tools, agent runtime
    How MCP works as a layer between tools and agents.

    MCP uses a client-server model over two transport mechanisms:

    • stdio: The MCP server runs as a local subprocess on your machine. Claude Code spawns it, communicates via standard input/output. This is the most common setup.
    • HTTP/SSE: The MCP server runs as a network service. Claude connects over HTTP with Server-Sent Events for streaming. Better for remote or shared servers.

    The communication protocol underneath is JSON-RPC 2.0 — a lightweight, well-understood standard for calling methods and getting results.

    Each MCP server exposes one or more of three primitives:

    • Tools: Functions Claude can call. Example: read_file(path), create_issue(title, body), run_query(sql). Claude decides when to call them based on context.
    • Resources: Data sources Claude can read. Example: the contents of a directory, a database schema, a project’s README. Resources are passive — they don’t take actions, they expose information.
    • Prompts: Reusable prompt templates that servers can provide to standardize how Claude interacts with them.

    When Claude sees a task that could benefit from an available tool, it calls the tool, receives the result, and incorporates it into the response. This happens automatically — you don’t have to tell Claude when to use MCP. Claude decides based on what the server exposes.

    MCP in Claude Code vs Claude Desktop

    Both Claude Code (the CLI tool) and Claude Desktop support MCP, but they configure servers differently.

    Claude Code

    Claude Code has built-in MCP management via the claude mcp command family:

    claude mcp add my-server -- npx -y @modelcontextprotocol/server-filesystem /path/to/directory
claude mcp list
claude mcp remove my-server

    Servers added with claude mcp add are stored in your Claude Code config (~/.claude.json or the project-level .claude/settings.json). Project-level configs let you commit MCP server setups to source control so the whole team gets them automatically.

    Claude Code also ships with a set of built-in tools that behave like MCP servers but don’t require separate installation: file read/write/edit, bash execution, glob search, grep, web fetch, and the agent spawning tools you’re reading about in this article.

    Claude Desktop

    Claude Desktop reads MCP server configuration from a JSON file:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
    • Windows: %APPDATA%\Claude\claude_desktop_config.json

    A typical config entry looks like this:

    {
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/Users/you/Documents"]
    },
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_your_token_here"
      }
    }
  }
}

    Restart Claude Desktop after editing the config. Each server you add appears in the Claude Desktop interface with a hammer icon, and Claude can access its tools in any conversation.

    The Most Useful MCP Servers

    Anthropic maintains a reference set of official MCP servers. These are the ones worth knowing:

    ServerWhat It DoesPackage
    FilesystemRead/write files and directories on your local machine@modelcontextprotocol/server-filesystem
    GitHubRead repos, create issues, open PRs, push code@modelcontextprotocol/server-github
    PostgreSQLRead-only SQL queries against a Postgres database@modelcontextprotocol/server-postgres
    SQLiteRead/write a local SQLite database file@modelcontextprotocol/server-sqlite
    Brave SearchLive web search via Brave’s Search API@modelcontextprotocol/server-brave-search
    PuppeteerHeadless browser — screenshot pages, scrape, fill forms@modelcontextprotocol/server-puppeteer
    SlackRead channels, send messages, search workspace@modelcontextprotocol/server-slack
    Google DriveRead and search Google Drive files@modelcontextprotocol/server-google-drive
    GitGit operations — log, diff, commit, branch management@modelcontextprotocol/server-git
    MemoryPersistent key-value knowledge graph across conversations@modelcontextprotocol/server-memory

    Beyond the official set, hundreds of community-built MCP servers cover everything from Notion and Linear to AWS and Docker. The MCP ecosystem grew faster than almost anyone expected after the November 2024 launch.

    Installing Your First MCP Server

    The fastest path is Claude Code with the filesystem server. This gives Claude read/write access to a directory you specify — useful for any project work.

    Prerequisites: Node.js installed (the server runs via npx).

    In your terminal:

    claude mcp add filesystem -- npx -y @modelcontextprotocol/server-filesystem ~/Documents/projects

    That’s it. Open a Claude Code session. Claude can now list, read, write, and search files inside ~/Documents/projects. Try: “List all Python files in this directory and summarize what each one does.”

    For Claude Desktop, edit the claude_desktop_config.json file directly (see format above), then restart the app.

    What MCP Cannot Do

    Five red warning rows of MCP limitations
    What MCP cannot do — permissions and review still matter.

    A few things worth understanding before you build on MCP:

    MCP servers don’t persist between conversations. Each Claude session starts fresh. If you need state persistence, you need a server with its own storage layer (the Memory server handles this specifically).

    MCP doesn’t bypass Claude’s safety guidelines. Claude still decides whether to execute a tool call based on safety and ethics reasoning. Connecting a filesystem server doesn’t give Claude unlimited license to delete files — Claude will still confirm before destructive operations.

    Subprocess MCP servers are local. The stdio transport runs servers on your machine. This means they only work when you’re running Claude Code locally. For remote or team-shared access, you need HTTP/SSE transport with a hosted server.

    Security Considerations

    MCP servers have real permissions. The filesystem server can read and write files. The GitHub server can push code to your repos. The Postgres server can run SQL queries.

    Apply the principle of least privilege:

    • Scope filesystem servers to the directory you actually need, not /
    • Use read-only database credentials where you don’t need writes
    • Create GitHub tokens with minimum required scope (e.g., repo for private repos, not org-level admin)
    • Never commit environment variables containing API keys to source control, even in .claude/settings.json — use env var references instead

    MCP servers run with the permissions of the user running Claude. If something goes wrong with a tool call, it can have real consequences. The upside: everything runs locally and through your own credentials — there’s no MCP cloud intermediary with access to your data.

    MCP and Claude Code’s Agentic Workflows

    The full power of MCP shows up in Claude Code’s multi-step agentic mode. When Claude Code has access to git, a filesystem, a browser, and a search tool simultaneously, it can execute workflows like:

    1. Search the web for a library’s current API (Brave Search)
    2. Read your existing code to understand the integration point (filesystem)
    3. Write the updated code (filesystem write)
    4. Run tests (bash)
    5. Create a PR (GitHub)

    Each of these steps would require a separate tool in a traditional automation stack. With MCP, Claude orchestrates all of them within a single session, using whatever servers are available.

    This is what makes MCP the infrastructure layer for agentic AI — not a feature, but the foundation that makes complex AI-driven workflows possible.

    Related on Tygart Media: Claude MCP · Skills vs MCP vs plugins · how to use Claude.

    Frequently Asked Questions

    What does MCP stand for?
    Model Context Protocol. It’s an open standard for connecting AI models to external tools, data sources, and services through a standard client-server interface.

    Who created MCP?
    Anthropic created MCP and released it as an open standard in November 2024. The specification and reference servers are open-source on GitHub. While Claude is the primary client, other AI systems can implement MCP clients too.

    Do I need to install MCP to use Claude?
    No. Claude works without any MCP servers. MCP is an extension layer — you add servers when you want Claude to access specific external systems. Claude Code also ships with a set of built-in tools (file operations, bash, web fetch) that don’t require MCP installation.

    Is MCP available on Claude.ai (the web app)?
    MCP server support is primarily in Claude Desktop and Claude Code. The Claude.ai web interface has its own tool integrations (web search, document analysis) but doesn’t support custom MCP servers in the same way.

    What’s the difference between MCP tools and Claude’s native tools in Claude Code?
    Claude Code’s native tools (Read, Write, Bash, Glob, Grep, WebFetch, Agent) are built into the application and don’t require a separate server process. MCP servers are external — they run as subprocesses or network services that Claude Code connects to. Both expose tools that Claude can call; the mechanism for loading them is different.

    How do I build my own MCP server?
    Anthropic provides official SDKs for building MCP servers in TypeScript, Python, Go, and other languages. The TypeScript SDK (@modelcontextprotocol/sdk) is the most mature. Start with Anthropic’s MCP documentation and the reference server implementations on GitHub as templates.

    Last verified: June 12, 2026. MCP specification and server ecosystem evolve quickly — check the official Anthropic MCP documentation for the current spec.

  • Claude Fable 5: Capabilities, Pricing (2026)

    Claude Fable 5: Capabilities, Pricing (2026)

    Anthropic released Claude Fable 5 on June 9, 2026 — and it’s the most capable model the company has ever made publicly available. After tracking every Claude release since the original 100K context window dropped, I can say this one is different. Fable 5 isn’t just an incremental update. It’s Anthropic’s Mythos-class model — the one they’d been keeping restricted — now opened up to anyone with an API key or a Claude subscription.

    Here’s what you need to know: the pricing, the benchmarks, and the specific decision framework for when to use Fable 5 versus sticking with Opus 4.8.

    Quick answer: Fable 5 costs $10/$50 per million input/output tokens (2x the cost of Opus 4.8). It outperforms Opus 4.8 significantly on complex coding, long-horizon tasks, and scientific research. Use Fable 5 when quality on hard problems justifies the cost. Use Opus 4.8 for high-volume, well-scoped, routine work.

    Current lineup note (October 2026): Fable 5.1 is the current Fable SKU at the same $10/$50 headline rates (cache reads $0.25/MTok). Current Opus is Opus 5.5 at $4/$20; Opus 4.8 remains listed as legacy. The June 2026 comparisons below are the launch record for Fable 5.

    What Is Claude Fable 5?

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    What is Claude Fable 5?

    Claude Fable 5 (claude-fable-5) is Anthropic’s first publicly available Mythos-class model. The Mythos line is Anthropic’s highest capability tier — models that were previously restricted to research and select enterprise partners because of their raw power. Fable 5 is the version Anthropic deemed safe enough to release broadly.

    The name shift (from the Opus/Sonnet/Haiku tier naming) signals something intentional. Fable 5 sits above the Opus line entirely. It’s a new ceiling.

    Key specs:

    • Context window: 1M tokens (same as Opus 4.8)
    • Max output: 128K tokens per request
    • Thinking: Adaptive (always on — not a separate “thinking mode”)
    • Vision: Yes
    • Tool use / function calling: Yes
    • Available: Claude API, AWS Bedrock, Vertex AI, Microsoft Foundry

    Claude Fable 5 Pricing

    Infographic ladder of Claude plans: Free, Pro, Max, Team, and Enterprise
    Fable 5 pricing — no sticky dollar stickers.
    ModelInput (per MTok)Output (per MTok)Context
    Claude Fable 5$10.00$50.001M tokens
    Claude Opus 4.8$5.00$25.001M tokens
    Claude Sonnet 4.6$3.00$15.001M tokens
    Claude Haiku 4.5$1.00$5.00200K tokens

    Fable 5 costs exactly 2x Opus 4.8 on API. On subscription plans (Pro, Max, Team, Enterprise seat-based), Fable 5 is included at no extra cost through June 22, 2026.

    The free-until-June-22 window matters if you’re evaluating whether to route your workloads to Fable 5. Use that window to benchmark it against your actual tasks before the 2x cost kicks in.

    Benchmark Performance: Where Fable 5 Pulls Away

    The benchmarks that matter most are the ones that measure what the model can do on real engineering work, not trivia:

    BenchmarkClaude Fable 5Claude Opus 4.8Delta
    SWE-bench Verified95.0%88.6%+6.4 pts
    SWE-bench Pro80.0%69.2%+10.8 pts
    FrontierCode29.3%13.4%~2.2x
    Senior Engineer benchmark91/100~63/100+45% absolute

    The Senior Engineer benchmark is the one I find most telling. It’s designed to be hard for people who write code for a living — and Fable 5 scores 45 percentage points higher than Opus 4.8. That gap is significant enough that it changes the calculus for serious engineering work.

    When to Use Claude Fable 5 (vs Opus 4.8)

    Decision fork between maximum capability when stakes are high and shipping daily when speed and cost matter
    When to use Fable 5 vs Opus.

    I’ve been routing tasks between models for long enough to have a framework. Here’s how I think about it:

    Use Fable 5 when:

    • You’re running a large migration, refactor, or multi-stage software project
    • Quality on a hard problem matters more than per-token cost
    • You’re doing deep research, complex analysis, or long-horizon agentic work
    • The task would otherwise take a senior engineer half a day or more
    • You’re in the free evaluation window (through June 22) and want to benchmark

    Use Opus 4.8 when:

    • The task is well-scoped and routine
    • You’re running high-volume pipelines where 2x cost compounds fast
    • Latency matters — Fable 5 can take 60 seconds to several minutes on complex tasks vs 3–15 seconds for Opus 4.8
    • The task falls in Fable 5’s restricted domains (cybersecurity, biology, chemistry, distillation) — in those categories, Fable 5 routes to Opus 4.8 anyway, so you’d pay Fable 5 prices for Opus 4.8 output

    The smart routing strategy: Fable 5 for the hard jobs, Opus 4.8 for the rest. Don’t use Fable 5 as your default model — the cost and latency delta aren’t worth it for routine tasks.

    Important Limitations to Know Before You Switch

    Two limitations that don’t get enough coverage:

    1. Safety classifier routing. Fable 5 includes enhanced safety classifiers. For prompts touching cybersecurity, biology, chemistry, and distillation, those classifiers route the request to a Claude Opus 4.8 fallback. You pay Fable 5 API rates ($10/$50) but get Opus 4.8 output. If your use case is in these domains, Fable 5 is not the upgrade it appears to be.

    2. Data retention requirement. Fable 5 carries a mandatory 30-day data retention policy — Anthropic needs retained prompts and outputs to operate the safety classifiers. Claude Opus 4.8 is available under zero data retention (ZDR). If your use case requires ZDR (healthcare, legal, finance with strict data handling), stick with Opus 4.8 until Anthropic updates Fable 5’s data policy.

    Availability

    Claude Fable 5 is generally available as of June 9, 2026 on:

    • Claude API (claude-fable-5)
    • Claude Platform on AWS / Amazon Bedrock
    • Google Cloud Vertex AI
    • Microsoft Azure AI Foundry / GitHub Copilot

    Subscription access (free through June 22, 2026): Claude Pro ($20/mo), Max 5x ($100/mo), Max 20x ($200/mo), Team, and seat-based Enterprise plans all include Fable 5 access at no extra charge during the launch window. After June 22, the plan-tier access picture may change — check Anthropic’s pricing page for updates.

    How This Changes the Claude Model Decision Tree

    Before Fable 5, the Claude decision tree was straightforward:

    • Need the best? → Opus 4.8
    • Need balance? → Sonnet 4.6
    • Need speed/cost? → Haiku 4.5

    Now it’s:

    • Hard problems, complex projects, long-horizon work → Fable 5
    • Everyday work, high-volume pipelines → Opus 4.8
    • Balance of cost and capability → Sonnet 4.6
    • Speed and cost optimization → Haiku 4.5

    The introduction of a model tier above Opus 4.8 doesn’t replace the existing lineup — it creates a new ceiling for the work that genuinely needs it.

    Related on Tygart Media: Fable 5 complete guide · Fable 5 firsthand · how to use Claude.

    Frequently Asked Questions

    Is Claude Fable 5 better than Opus 4.8?
    For complex coding, multi-stage tasks, and long-horizon work: yes, significantly. On SWE-bench Pro, Fable 5 scores 80.0% vs Opus 4.8’s 69.2% — a 10+ point gap. For routine, well-scoped tasks: the gap narrows enough that Opus 4.8’s 2x cost advantage makes it the smarter choice.

    What is the Claude Fable 5 API model ID?
    claude-fable-5. This is the API string you pass to model in your API calls.

    Does Fable 5 cost more than Opus 4.8?
    Yes — exactly 2x. Fable 5 is $10 input / $50 output per million tokens. Opus 4.8 is $5/$25. Through June 22, 2026, Fable 5 is included in Claude subscription plans at no extra cost.

    Can I use Claude Fable 5 for free?
    On Pro, Max, Team, and Enterprise subscription plans, yes — through June 22, 2026. API access is metered at $10/$50 per MTok from day one.

    Does Claude Fable 5 support zero data retention (ZDR)?
    No. Fable 5 carries a mandatory 30-day data retention requirement. If your use case requires ZDR, use Claude Opus 4.8, which supports it.

    What’s the difference between Claude Fable 5 and Claude Mythos 5?
    Mythos 5 is Anthropic’s fully restricted research model — not publicly available. Fable 5 is the Mythos-class model that Anthropic has prepared for general availability, with safety classifiers and the 30-day retention policy. You can think of Fable 5 as “Mythos for the real world.”

    Last verified: October 5, 2026. Anthropic pricing and availability subject to change — check Anthropic’s pricing page for current rates.

  • AEO Content Optimizer — Claude AI Skill for Featured Snippets

    AEO Content Optimizer — Claude AI Skill for Featured Snippets

    Paste your article. Get back the version built to win the featured snippet.

    Who This Is For

    Comparison of Claude how-to fit versus local service page fit for assistants
    Who the AEO content optimizer skill is for.

    Built for site owners and content marketers who publish good content that never gets picked as the answer — no featured snippets, no People Also Ask placements, invisible in voice results and AI Overviews while thinner competitor pages take the box.

    The Problem

    Answer engines do not reward the best content — they reward the most extractable content. A page that buries its answer in paragraph six loses to a page that answers in the first 50 words under a question heading, formatted the way the snippet wants. Restructuring for extraction is mechanical, learnable work — and almost nobody does it. This skill does it on every piece you paste.

    What It Does

    GEO versus SEO comparison cards
    What it does for featured snippets / AEO.
    • Performs answer-first surgery: a direct, self-contained 40–60 word answer placed immediately under each question heading
    • Converts topical headings into the question formats searchers actually use, mapped to real query variants
    • Matches the winning snippet format per query — paragraph, numbered list, or table — and rebuilds the block to fit
    • Builds a genuine FAQ section and generates the matching FAQPage JSON-LD (and warns about duplicate schema before you paste)
    • Runs a voice pass so direct answers survive a smart-speaker read
    • Returns a change log plus an honest note on what content is missing that the query demands

    What You Get

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    What you get.
    • The aeo-content-optimizer.skill file — installs in claude.ai or Claude Code in about two minutes
    • README with installation steps and tested example prompts
    • Works on existing posts, new drafts, and competitor-gap rewrites

    $47 one-time

    Buy Now →

    Secure checkout via Square — all major cards accepted

    Want a custom version built specifically for your business? Email will@tygartmedia.com

    Related on Tygart Media: GEO tactics · AEO content cluster · schema injection skill.

    Frequently Asked Questions

    Do I need technical knowledge to use this?

    No. You paste your content and your target question. The skill restructures and returns paste-ready output, including the schema block.

    Does it work for my niche?

    Yes — the method is format-driven, not topic-driven. Local services, SaaS, e-commerce, professional services, and content sites all follow the same extraction rules.

    Will it change my voice or facts?

    It restructures; it does not genericize. Anything it cannot verify is flagged for you to supply rather than invented.

    How is this delivered?

    Within 24 hours of purchase via email from will@tygartmedia.com. Skill file and setup guide delivered as a ZIP download.

    Does this require a paid Claude subscription?

    Installing as a custom skill requires a paid Claude plan (Pro, $20/mo, or higher) with code execution enabled. Your download also includes a free-plan setup option — paste the skill into a Claude Project’s instructions — that works on any plan.

  • How to Get an Anthropic API Key (2026 Quick Guide)

    How to Get an Anthropic API Key (2026 Quick Guide)

    Last verified: September 26, 2026 (Pacific Time)

    Direct Answer (September 2026): To obtain an Anthropic API key: 1) Register at console.anthropic.com, 2) Navigate to Settings > Plans & Billing and deposit $5+ for Tier 1 activation, 3) Go to ‘API Keys’, click ‘Create Key’, and copy your secure sk-ant-api03-... key token.

    macOS / Linux:
export ANTHROPIC_API_KEY="sk-ant-YOUR_KEY_HERE"
Windows (PowerShell):
setx ANTHROPIC_API_KEY "sk-ant-YOUR_KEY_HERE"

    Replace YOUR_KEY_HERE with the key shown once at creation — Anthropic never shows it again.

    An Anthropic API key is the secret token that authenticates your requests to Claude models over the API. It starts with sk-ant-, is created in the Anthropic Console at console.anthropic.com under API Keys → Create Key, and is displayed exactly once — requests only succeed after you add a payment method.

    Official links:Create a key (console) · API docs · API rates · Help center

    Quick answer: sign in at console.anthropic.com (it now redirects to the same developer console as platform.claude.com), add a payment method under Settings → Billing, click API Keys → Create Key, name it, and copy it immediately – Anthropic shows the key exactly once. Keys start with sk-ant-. The whole process takes about five minutes.

    Below is the full walkthrough, where to put the key so it doesn’t leak, the newer no-static-key option most tutorials haven’t caught up with, and the errors that account for nearly every failed first request. For the full reference – pricing tiers, key rotation, security, and workspace and organization keys – see our Anthropic API key reference and management guide.

    What you need before you start

    Desk with laptop, checklist notebook, and billing card ready before creating an Anthropic API key
    • An email address (or Google / SSO login)
    • A payment method – your key will not work until billing is set up, even though you can create one
    • Five minutes

    One distinction that confuses almost everyone: a Claude.ai subscription is not API access. Claude Pro, Max, and Team plans cover the Claude apps (web, desktop, mobile). The API is billed separately, by usage, through the developer console. You can have either one without the other – see our complete Claude pricing guide for how the two systems differ.

    Step 1: Create your account

    Open the Anthropic console ?

    Go to console.anthropic.com – Anthropic’s developer console. (Both console.anthropic.com and platform.claude.com land in the same place in 2026; older tutorials treat them as different sites.) Sign up with email, Google, or SSO, and answer the brief onboarding questions about whether you’re an individual or an organization. For a tour of everything inside the console, see our Anthropic Console guide.

    Step 2: Add billing

    Open billing settings ?

    In the console, open Settings → Billing and add a credit card (self-serve accounts typically purchase prepaid usage credits). Skipping this step is the #1 reason a brand-new key returns errors – the key exists, but requests are rejected until the account can be billed.

    Step 3: Create the key

    Create the key in the console ?

    Click API Keys in the left sidebar (direct link: platform.claude.com/settings/keys), then Create Key. Give it a descriptive name like my-app-dev – future you will thank present you when it’s time to rotate or revoke. If your organization uses multiple workspaces, note that keys are scoped to a workspace: the key only sees resources in the workspace it was created in.

    Step 4: Copy it immediately

    Developer copying a new API key into a password vault; secret string not readable

    The key is displayed exactly once. It starts with sk-ant- followed by a long string. Copy it straight into a password manager, a .env file, or your secrets manager. If you lose it, there is no way to view it again – you revoke it and create a new one (takes a minute, harms nothing).

    Where to put the key (and where never to put it)

    Diagram contrasting never places for API keys versus vault, env file, and secrets manager

    Set it as an environment variable named ANTHROPIC_API_KEY – every official Anthropic SDK reads that variable automatically, so your code never contains the key:

    • macOS / Linux:export ANTHROPIC_API_KEY=sk-ant-...
    • Windows (PowerShell):setx ANTHROPIC_API_KEY "sk-ant-..."
    • Python:client = anthropic.Anthropic() – no key argument needed
    • TypeScript:const client = new Anthropic() – same

    Never hardcode the key in source files, never commit it to a repository, and never paste it into a system prompt or chat message. Leaked Anthropic keys get scraped and drained like any other credential.

    The 2026 no-key option: OAuth login

    Newer than most guides: Anthropic’s CLI can authenticate without any static key. Run ant auth login and a browser window authorizes a short-lived OAuth profile on your machine – the SDKs and Claude Code pick it up automatically, and there is no permanent secret to leak or rotate. For CI servers and production workloads, Workload Identity Federation serves the same purpose. If you’re setting up a personal development machine in 2026, this is arguably the better default; create a static key when you need one for a deployed service.

    Test your key

    One request confirms everything works (Haiku keeps the test nearly free):

    curl https://api.anthropic.com/v1/messages 
 -H "x-api-key: $ANTHROPIC_API_KEY" 
 -H "anthropic-version: 2023-06-01" 
 -H "content-type: application/json" 
 -d '{"model": "claude-haiku-4-5", "max_tokens": 32, "messages": [{"role": "user", "content": "Say hello"}]}'

    A JSON response with a content array means you’re live.

    Troubleshooting the four common errors

    • 401 authentication_error – the key is missing, mistyped, or revoked. Subtle 2026 variant: if both ANTHROPIC_API_KEY and ANTHROPIC_AUTH_TOKEN are set, the SDK sends both and the API rejects the request – unset one.
    • 403 permission_error – the key works but lacks access to that model or feature; check your key’s workspace and your organization’s model access.
    • 429 rate_limit_error – you’re sending faster than your usage tier allows. The response includes a retry-after header; official SDKs retry automatically. For tier details and fixes, see our Claude rate limits guide.
    • Key created but every request fails – almost always billing not completed (Step 2).

    FAQ

    Is the Anthropic API free? No – it’s usage-priced per million tokens with no permanent free tier (current rates in our Claude pricing guide and API token rates schedule, including the September 2026 lineup).

    Where do I find my existing API key? You can’t – Anthropic shows keys only at creation. Revoke the old one and create a replacement.

    Where is the API Keys page in console.anthropic.com? Sign in at console.anthropic.com, choose API Keys in the left navigation — or go straight to platform.claude.com/settings/keys — then click Create Key.

    Does my Claude Pro or Max subscription include an API key? No. App subscriptions and API billing are separate systems; an API account starts at $0 and bills per token used.

    Lineup currency (Sept 2026, verified): Sonnet 5 ($2/$10), Opus 5.5 ($4/$20), Haiku 4.5 ($1/$5), Fable 5.1 ($10/$50). Legacy (still listed): Opus 4.8 ($5/$25), Sonnet 4.6 ($3/$15).

    Sources

    >Part of the complete guide: Claude Pricing, Plans & Limits

  • Claude AI Updates (June 2026): Fable 5 & Features

    Claude AI Updates (June 2026): Fable 5 & Features

    Last verified: August 26, 2026 (Pacific Time)May 2026 edition covered the Opus 4.8 launch, the SpaceX compute deal, and Managed Agents memory features.

    Direct Answer (August 2026 Update): Major mid-2026 Anthropic releases introduced Claude Fable 5, native Model Context Protocol (MCP) tool integration in Claude Desktop, extended 1M context beta on Vertex AI/AWS Bedrock, and decoupled Enterprise seat pricing.

    June 2026 is one of the biggest months for Anthropic since the Claude 4 launch: a new top-tier model is generally available, two workhorse models retire in four days, and Managed Agents can now run inside infrastructure you control. Here is everything that changed, with dates and migration paths.

    Claude Fable 5 — the Mythos-class model goes public (June 9, 2026)

    Abstract milestone timeline from early Claude eras through today without version numbers
    Fable 5 launch — keep the timeline abstract.

    Anthropic released Claude Fable 5 on June 9, 2026 — the public version of what had been known as its Mythos-class model tier. It is positioned as a new tier above Opus, and it is Anthropic’s most capable generally available model. According to CNBC’s launch coverage, Fable 5 scored more than 10% higher than Claude Opus 4.8 on some benchmarks, with exceptional performance across software engineering and knowledge work. Anthropic credits new safeguards that block responses in specific high-risk areas for making a broad release possible.

    The practical details developers need:

    • Model ID: claude-fable-5
    • Availability: enterprise customers and paid subscribers
    • Context window: 1 million tokens; maximum output 128K tokens
    • API pricing: $10 per million input tokens / $50 per million output tokens
    • API surface: adaptive thinking only — temperature, top_p, top_k, and budget_tokens are not accepted, and unlike Opus 4.8, an explicit thinking: {type: "disabled"} returns a 400 error. Omit the thinking parameter entirely if you do not want it.

    For where Fable 5 sits against every other Claude model on price, see our continuously updated Claude AI pricing guide, and our complete Fable 5 guide for capabilities and use cases.

    June 15 deadline: Claude Opus 4 and Sonnet 4 retire in four days

    If you are still calling claude-opus-4-20250514 or claude-sonnet-4-20250514, those models retire from the Claude API on June 15, 2026. Requests after retirement return 404 errors. The drop-in replacements:

    • claude-opus-4-20250514 → claude-opus-4-8
    • claude-sonnet-4-20250514 → claude-sonnet-4-6

    Note that both replacements use adaptive thinking rather than manual thinking budgets, and the 4.6+ models reject assistant-turn prefills — so this is a small migration, not just a string swap. Anthropic also deprecated Claude Opus 4.1 this month, with API retirement scheduled for August 5, 2026 — worth adding to your migration calendar now.

    Current Claude model lineup and API pricing (June 2026)

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    Current lineup by job — no sticky version stickers on art.
    Model Model ID Context Max output Input $/1M Output $/1M
    Claude Fable 5 claude-fable-5 1M 128K $10.00 $50.00
    Claude Opus 4.8 (legacy — still listed) claude-opus-4-8 1M 128K $5.00 $25.00
    Claude Opus 4.8 (legacy — still listed) claude-opus-4-8 1M 128K $5.00 $25.00
    Claude Sonnet 4.6 (legacy — still listed) claude-sonnet-4-6 1M 64K $3.00 $15.00
    Claude Haiku 4.5 claude-haiku-4-5 200K 64K $1.00 $5.00

    Opus 4.7, 4.6, 4.5, and 4.1 and Sonnet 4.5 remain active for pinned workloads. We track which model is current at any moment in our current Claude model version reference.

    Managed Agents: self-hosted sandboxes and private MCP servers

    Three stacked layers: chat UI, tools, agent runtime
    Managed Agents and private MCP servers.

    Claude Managed Agents — Anthropic’s server-managed agent platform — can now execute tools inside a sandbox you control. The agent loop still runs on Anthropic’s orchestration layer, but bash commands, file operations, and code execution happen in your own container, behind your own firewall, with your own egress rules. Your worker long-polls Anthropic’s work queue over outbound-only connections; Anthropic never dials into your network. Managed Agents can also now connect to private MCP servers, which matters for any organization whose internal tools are not on the public internet.

    For regulated industries — healthcare, finance, legal — this is the missing piece that lets you adopt hosted agents while keeping data residency: files and tool output never leave infrastructure you own.

    Claude Code: nested sub-agents and plugin search

    Claude Code shipped a steady stream of updates in June: nested sub-agents (agents can now spawn their own sub-agents for deeper task decomposition), smarter model and region handling, a new plugin search, and improved Chrome, VS Code, and terminal workflows.

    Legal expansion: 20+ MCP connectors and 12 practice-area plugins

    Anthropic released more than 20 new legal MCP connectors and 12 practice-area plugins, covering research, contracts, discovery, matter management, and legal aid. The pattern to note: Anthropic is increasingly shipping vertical integration bundles rather than leaving connector-building entirely to the ecosystem.

    Claude Corps: $150M for nonprofit AI adoption

    Anthropic announced Claude Corps, a $150 million fellowship program that will embed roughly 1,000 trained fellows inside nonprofit organizations for a year to help them use AI effectively. Applications and program details are rolling out through Anthropic’s newsroom.

    Apple Foundation Models integration

    Claude support is coming to Apple’s Foundation Models framework on iOS 27, iPadOS 27, macOS 27, and visionOS 27 — meaning third-party Apple developers will be able to call Claude through Apple’s native AI framework rather than integrating the API directly.

    What to watch for in July

    • August 5, 2026: Claude Opus 4.1 retires from the API — migrate to claude-opus-4-8 before then.
    • Fable 5 ecosystem: expect Claude Code, Cowork, and Managed Agents to expose Fable 5 more broadly through July as capacity scales.
    • Apple rollout: developer betas of the iOS 27 family will show what Claude-via-Foundation-Models actually looks like in practice.

    Sources

    💼 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 Complete Guide

    Claude Fable 5 Complete Guide

    
    New in 2026

    Everything you need to know about Anthropic’s new frontier tier — pricing, context window, model comparisons, and how to route the right work to the right model.

    Updated June 2026 · ~14 min read · Includes interactive calculators
    Lineup update (September 2026): Since this guide was last fully updated, Anthropic shipped Opus 5.5 ($4/MTok in, $20/MTok out) and Sonnet 5 ($2/MTok in, $10/MTok out) as its current flagship and mid-tier models. Fable 5.1 remains the top-tier model referenced throughout, at the same $10/$50 pricing shown below. Opus 4.8 and Sonnet 4.6 are now legacy — still supported, no longer current default.

    What Is Claude Fable 5?

    Three cards for fast volume, daily workhorse, and deep flagship Claude seats
    What is Claude Fable 5?

    Claude Fable 5 is Anthropic’s new frontier model tier — positioned above Opus in the lineup and designed for tasks where raw capability, extended reasoning depth, and massive context handling matter more than cost. Where Opus 4.8 set the bar for complex multi-step reasoning, Fable 5 raises it with a 1-million-token context window, enhanced agentic autonomy, and improved performance on long-horizon software engineering, research synthesis, and cross-domain analysis tasks.

    The “Fable” naming signals a new generation of model architecture rather than an incremental update. Anthropic positions it as the model you reach for when a task exceeds what Opus can do reliably — not as a replacement for Opus, Sonnet, or Haiku in their respective cost tiers.

    Quick Facts — Claude Fable 5

    Context Window
    1M
    tokens (~750K words)
    Max Output
    32K
    tokens per response
    Input Price
    $10
    per million tokens
    Output Price
    $50
    per million tokens
    Cache Write
    $12.50
    per million tokens
    Cache Read
    $1.00
    per million tokens
    Key positioning: Fable 5 is the model for tasks where Opus 4.8 produces reliable but imperfect results — long codebase audits, full-document analysis, complex multi-agent orchestration, and strategic synthesis across large corpora. For most production workflows, Sonnet remains the value pick.
    Before you price this out: The table below reflects the June 2026 lineup (Fable 5, Opus 4.8, Sonnet 4.6, Haiku 4.5). As of September 2026, Opus 5.5 ($4/$20) and Sonnet 5 ($2/$10) are Anthropic’s current models — priced lower than the legacy Opus 4.8 / Sonnet 4.6 rows shown here.

    Full Model Lineup Comparison

    Pyramid diagram of Claude tiers: fast volume base, production workhorse middle, deep flagship peak
    Full model lineup comparison.

    Here’s how the complete 2026 Claude lineup stacks up across every dimension that matters for production usage:

    Model Input $/M Output $/M Context Max Out Vision Tool Use Extended Think Best For
    ◆ Fable 5 $10 $50 1M 32K ✓ ✓ ✓ Deep Max-capability tasks, 1M+ context
    ◆ Opus 4.8 $5 $25 200K 32K ✓ ✓ ✓ Complex reasoning, agentic workflows
    ◆ Sonnet 4.6 $3 $15 200K 16K ✓ ✓ ✓ Production apps, content at scale
    ◆ Haiku 4.5 $1 $5 200K 8K ✓ ✓ — High-volume, latency-sensitive tasks

    Prices are per million tokens. Cache read is 90% cheaper than standard input across all models. Batch API provides an additional 50% discount on both input and output.

    Capability Matrix — What Each Model Can Do

    Capability Fable 5 Opus 4.8 Sonnet 4.6 Haiku 4.5
    Full codebase analysis (>500K tokens)✓ Native⚠ Chunked✗✗
    Extended thinking / chain-of-thought✓ Deep✓✓✗
    Multi-step agentic orchestration✓ Best✓GoodLimited
    Computer use✓✓✓✗
    MCP tool integration✓✓✓✓
    Prompt caching✓✓✓✓
    Batch API (50% discount)✓✓✓✓
    PDF / document analysis✓✓✓Limited
    Real-time streaming✓✓✓✓
    Structured JSON output✓✓✓✓

    Interactive Cost Calculator

    Estimate your monthly API spend across the full model lineup. Enter your token volumes below — the calculator models prompt caching and Batch API discounts automatically.

    Token Cost Calculator

    Estimated Monthly Cost
    $0.00

    Which Claude Model Should You Use?

    Decision diagram from task shape to deep reasoning, daily shipping, or high-volume cheap calls
    Which Claude model should you use?

    Answer three questions to get a model recommendation tailored to your use case.

    Model Picker — 3 Questions
    1. How large is your context? (document/codebase size)
    Under 50K tokens
    50K–200K tokens
    200K–1M tokens
    2. How complex is the task?
    Simple / structured (classify, extract, format)
    Moderate (draft, summarize, QA)
    Complex (reason, plan, code, orchestrate)
    3. How cost-sensitive is this workload?
    Very — high volume, every cent counts
    Moderate — quality matters more than cost
    Not sensitive — quality and capability first

    How We Actually Use Each Model

    These are real production workflows mapped to the right tier — built from running Claude in content operations, publishing automation, and knowledge management at scale. No hypotheticals.

    Haiku 4.5 — High Volume
    Daily SEO Refresh Pipeline
    • 25-post-per-day SEO metadata refresh
    • Article classification and tag assignment
    • Structured data extraction from web pages
    • Keyword density checks across large post archives
    • Link validation and redirect flagging
    Sonnet 4.6 — Production Default
    Editorial Content at Scale
    • Desk article writing (1,200–2,500 words)
    • Content brief execution from keyword clusters
    • FAQ and schema markup generation
    • Cross-site content adaptation and localization
    • Monthly client update drafts and summaries
    Opus 4.8 — Complex Reasoning
    Workers & Deep Refreshes
    • Agentic Notion Workers (multi-step pipelines)
    • Deep content refresh with competitive gap analysis
    • Multi-database synthesis and reporting
    • Strategy documents requiring extended reasoning
    • Code generation for automation scripts
    Fable 5 — Max Capability
    Portfolio Audits & Strategy
    • Full-site content audits (500+ posts in single context)
    • Cross-domain strategy synthesis across large corpora
    • Complex multi-agent orchestration at the flagship tier
    • Long-horizon planning requiring deep reasoning depth
    • Codebase-wide analysis and architecture review
    Routing principle: The right model is the cheapest one that reliably completes the task. Haiku handles volume. Sonnet handles production. Opus handles complexity. Fable 5 handles scale + complexity together — specifically the cases where you’d need Opus and more context than Opus can hold.

    The Economics: Routed vs All-Fable

    Smart model routing is where API costs get controlled. Here’s a real-world comparison of a mixed content-and-automation workload at scale — routed vs running everything on Fable 5.

    Workload Monthly Volume Routed Model Routed Cost All-Fable 5 Cost Savings
    SEO metadata batch refresh750 posts/moHaiku 4.5 + Batch$1.20$18.7593% less
    Article drafting90 articles/moSonnet 4.6$8.10$67.5088% less
    Agentic worker runs200 runs/moOpus 4.8$22.50$45.0050% less
    Full-site portfolio audits4 audits/moFable 5$24.00$24.00—
    Total—Routed$55.80$155.2564% less

    Stacking Discounts: Caching + Batch API

    Two discount mechanisms compound independently:

    • Prompt caching: Cache your system prompt and shared context once. Subsequent requests pay ~10% of the input price for cache reads. On Fable 5, that’s $1.00/M instead of $10.00/M on cached tokens — a 90% reduction on your largest cost lever.
    • Batch API: Submit requests asynchronously (results within 24 hours) for a flat 50% discount on both input and output. Works on all four models. Best for non-real-time workloads like overnight refreshes, audits, or bulk classification.
    • Stacked: Caching + Batch combined can bring effective Fable 5 input cost from $10/M to ~$0.50/M on cached tokens — making it economically viable for high-volume tasks that previously only fit Haiku’s budget.

    See our Claude context window guide for more on how to structure prompts to maximize cache hit rates.

    Related Claude Resources

    Claude Context Window Guide Claude Projects Deep Dive Claude Code Plan Mode Claude MCP Setup Guide Opus 4.7 Feature Deep Dive Claude Code vs Cursor (2026)

    Claude Fable 5 FAQ

    Claude Fable 5 sits above Opus 4.8 in the lineup. The primary difference is context window size — Fable 5 offers 1 million tokens vs Opus 4.8’s 200K — and the depth of extended reasoning for highly complex tasks. Opus 4.8 remains the right choice for most complex agentic workflows at half the cost. Fable 5 is best when you need both maximum context and maximum reasoning depth simultaneously, or when a task has routinely hit the limits of what Opus can do reliably.
    Claude Fable 5 is priced at $10 per million input tokens and $50 per million output tokens — 2× Opus 4.8 ($5/$25), 3.3× Sonnet 4.6 ($3/$15), and 10× Haiku 4.5 ($1/$5). Prompt caching drops the effective input cost to $1.00/M on cache reads, and the Batch API adds a 50% discount on all tokens for non-real-time workloads. Stacking both discounts makes Fable 5 viable for higher-volume use cases than the base price suggests.
    Claude Fable 5 has a 1-million-token context window — approximately 750,000 words or roughly 1,500 pages of text. This is 5× the context window of Opus 4.8, Sonnet 4.6, and Haiku 4.5 (all 200K). In practice, a 1M context window lets you pass entire codebases, long research corpora, or full document archives in a single API call without chunking or retrieval workarounds. For more on context window mechanics, see our full context window guide.
    Yes. Claude Fable 5 is available through the Anthropic API using the model ID claude-fable-5-20260101 (check the Anthropic documentation for the exact identifier). It supports the same API surface as the rest of the Claude family — streaming, tool use, prompt caching, vision, the Batch API, and MCP server integration. Access requires an Anthropic API account with Fable 5 enabled on your usage tier.
    Fable 5 is available in Claude.ai on the Pro and Team plans. The interface lets you select it from the model picker when starting a conversation. Like Opus, Fable 5 in claude.ai has message limits that reset on a rolling window — it’s designed for individual complex tasks rather than high-volume API workloads. For production-scale usage, the API with the Batch API discount is the more economical path.
    Yes — and Fable 5’s extended thinking is the deepest in the lineup. Where Opus 4.8 supports extended thinking for complex reasoning tasks, Fable 5 uses a more capable reasoning engine designed for tasks that require longer chains of inference, more working memory, and more reliable self-correction. It’s particularly effective on math, logic, long-horizon planning, and tasks where the model needs to hold and manipulate many interdependent concepts simultaneously.
    For most content production — articles, blog posts, social copy, summaries, SEO content — Sonnet 4.6 is the right call. It produces high-quality output at 3.3× less cost than Fable 5, and for typical content lengths (500–3,000 words), the quality difference is minimal. Reach for Fable 5 when you need to synthesize across a very large corpus (e.g., auditing 200+ posts simultaneously), when the content requires deep domain reasoning that benefits from extended thinking, or when the task involves both large-context ingestion and complex output generation in a single pass.
    Three levers in order of impact: (1) Model routing — only use Fable 5 when the task genuinely requires it; route everything else to Opus, Sonnet, or Haiku based on complexity and volume. (2) Prompt caching — structure your system prompt and shared context so it can be cached; cache reads cost $1.00/M instead of $10.00/M on Fable 5. (3) Batch API — submit non-real-time workloads via the Batch API for a flat 50% discount. Stacking all three — routing + caching + batch — can reduce effective per-task costs by 85–95% compared to unoptimized Fable 5 calls.

    More Claude Guides from Tygart Media

    We run Claude in production every day. These are the guides that come from using it, not just writing about it.

    Context Window Guide Claude Projects Plan Mode MCP Setup Code vs Cursor

    Related on Tygart Media: Claude Fable 5 overview · Fable 5 firsthand · Claude pricing.

  • Platform-Specific AI Optimization (PSAO): The Definitive Framework for 2026

    Platform-Specific AI Optimization (PSAO): The Definitive Framework for 2026

    Platform-Specific AI Optimization (PSAO) is the practice of tailoring content strategy to the distinct user personas, retrieval mechanisms, and citation patterns of each individual AI search platform. It replaces the outdated approach of “optimizing for AI” as though AI were a single channel with a single audience.

    This article defines PSAO, maps the six major platforms, profiles their user personas, and provides the operational checklist. It’s the synthesis of the entire PSAO editorial sprint into a single reference document.

    Why PSAO Exists

    Six evaluation cards for choosing an AI assistant platform
    Why PSAO exists — optimize per platform.

    The phrase “optimize for AI” is as meaningless as “optimize for social media.” You wouldn’t write the same post for LinkedIn and TikTok. You shouldn’t write the same content for Perplexity and Copilot. Each AI platform has a different user base, different query patterns, different retrieval infrastructure, and different citation mechanics.

    PSAO emerged from practical necessity. Managing content across 20+ WordPress sites and tracking citation data — including 98,800 Copilot grounding citations from a single property — made the platform-level differences impossible to ignore. Content that earned citations on Copilot performed differently on Perplexity. Articles that won Google AI Overviews weren’t the same articles ChatGPT cited. The patterns were consistent and structural, not random.

    The 6 PSAO Platforms

    Platform 1: Perplexity

    User persona: Researcher, analyst, fact-checker. Chose Perplexity specifically for inline citations and multi-source verification.
    Query style: Multi-part, complex, verification-oriented.
    Content that wins: Primary source data, methodology explanations, comprehensive structured guides with numbered steps.
    Retrieval: Bing index + proprietary crawling. Inline numbered citations visible to users.
    Key metric: Citation frequency across diverse query types.

    Platform 2: Microsoft Copilot

    User persona: Enterprise knowledge worker in Microsoft 365. Mid-task, time-pressured, gap-filling.
    Query style: Short, specific, definitional. Pricing, comparisons, quick facts.
    Content that wins: Pricing tables, comparison charts, FAQ format, definitive statements in professional tone.
    Retrieval: Bing index for grounding. Footnote-style citations users rarely check.
    Key metric: Grounding citation count (tracked via Bing Webmaster Tools AI Performance).

    Platform 3: Google AI Overviews

    User persona: Traditional Google searcher. Didn’t choose AI — it appeared automatically above organic results.
    Query style: Standard Google search — informational, definitional, how-to.
    Content that wins: Direct answer in first paragraph, schema markup, concise FAQ, entity-rich text.
    Retrieval: Google index + Knowledge Graph. Small source chips below overview.
    Key metric: AI Overview appearance rate and click-through from source chips.

    Platform 4: ChatGPT

    User persona: Explorer, creator, problem-solver. Iterates through multi-turn conversations.
    Query style: Conversational chains of 3-7 queries, each building on the previous. Code paste-ins, brainstorming.
    Content that wins: Deep technical guides, tutorials with working examples, analytical frameworks that provoke further thinking.
    Retrieval: Bing index via ChatGPT Search + OAI-SearchBot. End-of-response source links.
    Key metric: Referral traffic quality (session duration, pages per session).

    Platform 5: Claude

    User persona: Builder, analyst, long-context thinker. Developers, engineers, technical operators.
    Query style: Complex analysis, code review, architectural decisions, document synthesis with 50K-200K token contexts.
    Content that wins: Technical deep-dives, honest trade-off analysis, decision frameworks, comparison matrices.
    Retrieval: No native web search (mid-2026). Influence through training data, Claude Projects, MCP integrations.
    Key metric: Content adoption as reference material, training data influence.

    Platform 6: Gemini

    User persona: Google Workspace native. Interacts with Gemini as a Google feature, not an AI product.
    Query style: Factual lookups, data analysis, document summarization — embedded in Workspace apps.
    Content that wins: Structured data, HTML tables, definitive factual statements, reference material.
    Retrieval: Google index + Knowledge Graph. Expandable source section.
    Key metric: Schema markup coverage and structured data richness.

    The PSAO User Persona Map

    PlatformPersonaIntentTime BudgetCitation AwarenessContent Format
    PerplexityResearcherDeep investigationMinutes to hoursHigh — demands sourcesGuides, data, methodology
    CopilotEnterprise workerGap-fill mid-taskSecondsLow — ignores footnotesTables, FAQ, pricing
    Google AIOTraditional searcherQuick answerSecondsLow — doesn’t noticeDirect answer, schema, FAQ
    ChatGPTExplorer/creatorIterate and exploreMinutesModerateTutorials, analysis, depth
    ClaudeBuilder/analystComplex analysisMinutes to hoursSelf-verifiesTrade-offs, decisions, tech
    GeminiWorkspace nativeFactual lookupSecondsLow — “it’s Google”Tables, facts, reference

    The PSAO Operational Checklist

    Four cards for content, ops, build, and knowledge work with Claude
    PSAO operational checklist.

    Use this checklist for every article before publishing. Each item maps to a specific platform’s citation requirement:

    Content Structure

    • Direct answer in first paragraph, under 100 words (Google AIO, Gemini)
    • 5-8 H2 sections, each answering a distinct sub-question (Perplexity)
    • FAQ section with 5-8 exact-match Q&A pairs (Copilot, Google AIO)
    • At least one HTML comparison or pricing table (Copilot, Gemini)
    • Technical depth section with specific implementation details (ChatGPT, Claude)
    • Trade-offs and limitations explicitly documented (Claude)

    Technical Implementation

    • Article JSON-LD schema (all platforms)
    • FAQPage JSON-LD schema (Copilot, Google AIO)
    • HowTo schema if applicable (Google AIO)
    • BreadcrumbList schema (Google AIO, Gemini)
    • Submitted to Google Search Console (Google AIO, Gemini)
    • Submitted to Bing Webmaster Tools (Copilot, ChatGPT, Perplexity)
    • IndexNow configured for immediate indexing (Copilot, ChatGPT, Perplexity)

    Content Quality

    • Factual density: specific, citable claims in every section (all platforms)
    • Entity-rich: named products, companies, standards, technologies (Gemini, Google AIO)
    • Professional tone suitable for pasting into business documents (Copilot)
    • Primary source data or first-party metrics where possible (Perplexity)
    • Working examples, code samples, or configurations where relevant (ChatGPT, Claude)

    Distribution

    • Update cadence established (monthly minimum for competitive topics)
    • Internal links to and from related content (all platforms — authority signal)
    • External citations to authoritative sources within the article (Perplexity — authority chain)

    PSAO vs Traditional SEO vs GEO vs AEO

    GEO versus SEO comparison cards
    PSAO vs traditional SEO vs GEO vs AEO.

    PSAO is not a replacement for SEO, GEO (Generative Engine Optimization), or AEO (Answer Engine Optimization). It’s the platform-specific layer that sits on top of those disciplines:

    DisciplineFocusGranularity
    SEOGoogle organic search rankingsGoogle-specific
    AEOFeatured snippets, People Also Ask, voice searchGoogle-specific
    GEOAI citation across all platformsAI as a monolith
    PSAOPlatform-by-platform AI optimizationIndividual platform personas

    GEO says “optimize for AI.” PSAO says “optimize for this AI platform’s specific user, specific retrieval mechanism, and specific citation pattern.” It’s the same difference between “do social media marketing” and “run a LinkedIn thought leadership strategy targeting VP-level decision makers in B2B SaaS.”

    Implementing PSAO at Scale

    For a single site, the PSAO checklist is manual. For managing multiple sites — which is the reality of agency work and portfolio management — PSAO needs automation:

    1. Schema injection automation: Every article gets Article + FAQPage schema automatically as part of the publishing pipeline
    2. Dual-index submission: Every new post submits to both Google Search Console and Bing Webmaster Tools via IndexNow
    3. Content structure templates: Writers start with the 6-layer template, ensuring every article has the direct answer, structured sections, FAQ, tables, and technical depth
    4. Update scheduling: Top-performing articles are flagged for monthly refresh with current data and examples
    5. Citation monitoring: Bing AI Performance data is reviewed weekly to track grounding citation trends and identify content that’s earning (or losing) citations

    Actionable Takeaways

    1. Adopt PSAO as a named discipline. Stop saying “optimize for AI.” Start specifying which platform and which user persona you’re targeting
    2. Use the PSAO checklist for every article. Print it, pin it, make it a template in your CMS. Every item maps to a real citation opportunity
    3. Submit to both Google and Bing. Three of six platforms use Bing. This is the most common infrastructure gap
    4. Write for the persona, not the algorithm. The Perplexity researcher wants different content than the Copilot enterprise worker. The structure follows from the persona
    5. Measure platform-level performance. Track citations, referral traffic, and conversion rates by AI platform — not “AI” as a single bucket

    FAQ

    What is Platform-Specific AI Optimization (PSAO)?

    PSAO is the practice of tailoring content strategy to the distinct user personas, retrieval mechanisms, and citation patterns of each individual AI search platform — Perplexity, Copilot, Google AI Overviews, ChatGPT, Claude, and Gemini — rather than treating AI as a single optimization target.

    How is PSAO different from GEO (Generative Engine Optimization)?

    GEO treats AI search as a monolith — optimizing for “AI” broadly. PSAO operates at the individual platform level, recognizing that each platform serves a different user persona with different content preferences and different citation mechanics. PSAO is the platform-specific layer that sits on top of GEO.

    Do I need to create different content for each AI platform?

    No. A single well-structured article can serve all six platforms using the PSAO 6-layer template: direct answer first, comprehensive structured body, FAQ section, technical depth, HTML tables, and schema markup. Each layer maps to a specific platform’s citation trigger.

    What is the PSAO checklist?

    The PSAO checklist is a pre-publish quality gate covering content structure, technical implementation, content quality, and distribution. Each item maps to a specific AI platform’s citation requirements, ensuring every article has maximum citation surface area across all six platforms.

    Which AI platform should I prioritize for PSAO?

    Prioritize based on your audience. If your audience is enterprise workers, prioritize Copilot optimization. If your audience is researchers, prioritize Perplexity. For maximum coverage with minimum effort, use the unified 6-layer article structure and the PSAO checklist to serve all platforms simultaneously.