Tag: Anthropic

  • Receipts: One Week, 6,753 Bot Visits, Three Kinds of Bots

    Receipts: One Week, 6,753 Bot Visits, Three Kinds of Bots

    “AI traffic” sounds like one thing. On the dashboard it is three different things, doing three different jobs, and they are not interchangeable.

    Healthcare Facility Hub, last 7 days: 6,753 AI-bot requests. The operators alone are a crowd — Microsoft 1,250, Meta 1,046, Google 646, OpenAI 580, Amazon 564, Anthropic 505, Perplexity 444, Huawei 401, ByteDance behind them, and a tail that runs down to a single visit each from names most site owners have never heard of.

    Clarity sorts them by what they came to do. AI Crawlers made 5,139 of the visits, 76.10% — the index builders, reading everything so the models know it exists. AI Search made 1,031, 15.27% — bots fetching a page because somebody just asked a question: PerplexityBot 444 of them, plus Lyrenth and Parallel. AI Assistants made 583, 8.63% — browsing on behalf of a person mid-conversation: OpenAI 320, Anthropic 94, DuckDuckGo 17, Cohere exactly 1.

    The distinction matters because each kind wants something different from a page. A crawler wants it complete and clean. A search bot wants the answer findable in seconds. An assistant wants the page to make sense lifted out of context. One page, three readers, three jobs.

    And for all 6,753 visits, the scrape-to-referral ratio is 535:1. One referral came back all week. The most-wanted page on the site, by the way, is not the homepage — it is a field sheet, /email-my-field-sheet/, with 885 requests, 13.11% of everything the bots did.

    Ask for receipts.

  • Move the Design System Before December 14 — the Chat Does Not Come With It

    Move the Design System Before December 14 — the Chat Does Not Come With It

    The standalone Claude Design site at claude.ai/design closes on December 14, 2026. After that date, the address opens Claude. Anthropic’s announcement gives the reason in one sentence: “Running two versions slows down fixes for both, so we’re folding the standalone site into Claude.”

    The migration that Anthropic offers moves design systems. It does not move projects. And the parts of your work that live only in the standalone product — the chats, the comments, the originals — have a deletion date, not a transfer path. This is the procedure for a team that has brand systems and client one-pagers in there, in the order the steps have to happen.

    What gets deleted, exactly

    Anthropic’s migration guide names the deletion list in two bullets: “Your chats with Claude” and “Comments on your projects and design systems.” Those stay in the standalone version and are deleted after it closes, per Anthropic’s data retention practices.

    Your originals are a separate statement, in the guide’s FAQ: they keep working in the standalone version until it closes on December 14, 2026, and “after that, they’re deleted.” A design system you migrate leaves its original behind in the standalone product, unchanged — and that original is on the same clock.

    Public links to standalone projects are a third outcome, and the guide words it differently on purpose: they “will no longer work after it closes.” Not deleted — dead. Every client you sent a public project link to holds a URL with an expiry date.

    The instruction Anthropic prints is the whole strategy for this section: save anything you need from your chats and comments before the standalone version closes. No fetched Anthropic page documents an export for chats or comments. The capture that matches the documentation is a screenshot of each comment thread and a copy of the chat text, done by hand.

    The dangerous sentence: “You don’t need to do anything with your projects yet”

    That sentence is in the migration guide, and it is true — your projects keep working in the standalone version until the close. It is also the sentence that will get client work deleted, because projects are the files with no migration path and a deadline.

    The Artifacts page in Claude lists up to 60 of your standalone projects, and they open in the standalone version. That list is a directory back into the product that is closing. It is not a move, and it is not a complete inventory if your team has made more than 60 projects. Anthropic’s position, in the guide’s words: “More details about moving your projects to Claude are coming soon.” Soon is doing a lot of work in that sentence, and December 14 is 56 days out.

    So the inventory step happens in the standalone product itself, not on the Artifacts list. Walk the standalone library for every client one-pager, deck, and brand system — including everything past the first 60 the Artifacts page shows.

    Before anyone clicks Migrate: the sharing problem

    One migration brings over every design system in your organization, including other people’s. It only needs to be started once — and anyone who can use Claude Design can start it, not just the organization’s owners. On individual plans there is no confirmation step at all: click, and it starts.

    The consequence that matters for a shop holding more than one client’s brand: “Published design systems that aren’t private will be shared with everyone in your organization and appear in their design system menu.” A system you published so your own projects would use it becomes an entry in every teammate’s menu the moment anyone runs the migration. On individual plans, nothing is shared — this is a team and organization trap, not a solo one.

    The precaution has to happen before the first click, because undoing it is not documented. In the standalone product, the setup guide names the Published toggle as the control that makes a system the organization’s working system. For every design system that should not appear in the whole organization’s menu, turn that toggle off first. A second migration is not a way back: a later run leaves an unchanged system alone and skips one that has changed inside Claude, so neither pass pulls a system out of the menu.

    Two kinds of systems do not migrate at all, no matter who clicks: “Empty design systems aren’t migrated, and neither are ones made from a built-in starter theme, even if you’ve edited them.” If your house brand began life as a starter theme you customized, the migration will silently leave it behind. There is no documented design-system export to fall back on. Copy the source assets out by hand before December 14.

    The export drill: one project, one zip

    There is no bulk download. Anthropic’s FAQ is blunt: “Not all at once. You can download them one at a time.” Open the project in the standalone version, click Share, choose “Project HTML” — for a slide deck, that item hides under “More formats and apps” — keep “Project archive” selected, and click Export.

    You get a .zip file with every file in the project. It is free and does not count toward your usage limits. Repeat it for every client one-pager and deck you cannot afford to lose, and store the zips outside Claude.

    Know what the zip is not. It is documented as every file in the project. Chats are on the deletion list, and no Anthropic page says the conversation comes along inside the archive. The zip preserves the files. The reasoning your team talked through in chat, and the client’s comments on the work, survive only if you captured them in the previous step.

    Enterprise: three switches, and one hard stop

    On Enterprise plans the migration is gated by settings that are easy to flatten into one wrong sentence, so take them separately. Artifacts themselves must be on — if they are off, people cannot migrate anything and will not even see the “Claude Design lives here now” banner.

    Design systems are a separate template switch: on for Team plans, off for Enterprise until an owner turns on Design systems in Organization settings > Artifacts. That is a different switch from Design and Slides, which Anthropic’s pages say were set to turn on by default on October 15, 2026 — a date that has now passed, with the help text still printing the scheduled sentence, so check your own settings rather than assuming either state. On plans with custom roles, each role also needs the Artifacts permissions, and a design system cannot be migrated if its owner’s role does not include design systems.

    The hard stop: “Organizations with zero data retention (ZDR) can’t turn on artifacts, so they can’t migrate.” If that is your organization, the migration procedure does not exist for you. The guide’s path is the per-project download, done before the close, one zip at a time.

    One more setting that does not do what an admin might hope: the Enterprise custom-retention article states that custom retention periods “do not apply to Claude Design.” The retention dial your organization already configured is not the instrument that keeps or deletes standalone chats, comments, or originals. The closure is.

    After it lands

    A migrated design system keeps its files as they were, and it cannot be hand-edited on its page yet. Its editors see the note: “Migrated from the standalone version. Ask Claude to make changes.” The editing model for a migrated brand system is a conversation, not a settings page.

    If someone edits a migrated system inside Claude and you later run the migration again, that system is listed under Skipped — “changed on claude.ai, left as they are” — so your edits are not overwritten. Replacing it with a fresh copy is a deliberate act: duplicate it first if the Claude-side changes matter, delete it in Claude, then migrate again.

    New design work lives in three doors now: any chat (ask for a design, or Output > Design in the message box), the Artifacts tab, and Claude Code, with /design to create, edit, and sync designs and /design-sync to pull in your design system. All of it draws on the same usage pool as the rest of Claude, including Claude Code — the separate weekly Claude Design allowance the product launched with is already gone, per the get-started guide.

    Two gaps in the new home are worth knowing before you move the team: Claude Design does not have version history yet, and inline comments there occasionally fail to appear on the page — Anthropic’s own workaround is to paste the feedback into the chat instead. The standalone product’s comment threads, the ones being deleted in December, are still the reliable record until you screenshot them.

    The order is the procedure

    Inventory in the standalone product. Turn off Published on anything that must not become an organization-wide menu entry. Mark the empty and starter-theme systems the migration will refuse, and copy their assets out by hand. Export every project that matters, one zip at a time. Screenshot the comments and copy the chats. Only then — owners having turned on Artifacts, Design systems, and the role permissions — does one person click Migrate, read the results window, and fix any failed system in the standalone product before running it again.

    Do those steps in that order and December 14 is a non-event: the address starts opening Claude, and everything you cared about is already there or already saved. Do them out of order — migrate first, inventory later — and the button will happily move the systems while the projects, comments, and originals sit in a product with 56 days left on it. We track vendor surface changes like this one on the desk because the procedure is always in the help pages; it is just never in the announcement. The announcement for this closure said chats and comments “won’t be available.” The help center is the text that says deleted.

    Sources: Anthropic’s migration guide, Migrate from standalone Claude Design to Claude, and the get-started guide, Get started with Claude Design, both read in full on October 19, 2026. A related surface change, worked the same way: Cursor’s shareable canvases, and how we check a vendor’s what’s-new claims in What’s New in Cursor Is a Claim.

  • Claude Haiku 5.5 Lists at $0.10 / $0.50 — Sonnet 5.5 Cache Reads Halved

    Last refreshed: October 8, 2026 (Pacific)

    Anthropic launched Claude Haiku 5.5 on October 7, 2026. Seat prices on claude.com did not move. The operator event is a new SKU at a lower unit price, plus a cache-read cut on Sonnet 5.5.

    Official sources: anthropic.com/claude-haiku-5-5, platform.claude.com pricing, October 7 rate card, claude.com/pricing.

    What changed

    Haiku 5.5 is a new SKU. It is not a rename of Haiku 4.5. Haiku 4.5 remains on the list at $1 / $5. Anthropic says about 90% of prior Haiku requests were under 100,000 tokens, which is the cheaper band.

    Haiku 4.5Haiku 5.5 ≤100kHaiku 5.5 >100k
    Input / MTok$1$0.10$0.50
    Output / MTok$5$0.50$2.50
    Cache write (5-minute)$1.25$0.125$0.625
    Cache read$0.10$0.01$0.05
    Batch input / output$0.50 / $2.50$0.05 / $0.25$0.25 / $1.25

    Sonnet 5.5 input and output did not move. Cache reads did: $0.20 to $0.10 per million tokens. Anthropic says that is about 20% cheaper on most agentic work because cache reads are a large share of the bill. Sonnet 5 cache reads stay $0.20. Opus 5.5 stays $4 / $20 with cache reads at $0.20.

    Do not average the two Haiku 5.5 bands. A prompt over 100,000 tokens pays the higher line. Haiku 5.5 also uses the newer tokenizer, so the same text can be more tokens than Haiku 4.5. The posted rate is not the whole bill.

    What did not change

    Free $0. Pro $20 monthly / $17 annual. Max 5x $100 and Max 20x $200 on the web Help Center. Team Standard $20 annual / $25 monthly per seat. Team Premium $100 annual / $125 monthly. Enterprise $20/seat plus usage at API rates. Cursor Pro stays $20; Pro+ $60; Ultra $200; Teams $40/user on cursor.com/pricing, with Teams Premium $120 on the docs page.

    Anthropic said it will roll out monthly Claude Platform credits this week: Max 5x $100, Max 20x $200, Team up to $500 pooled. That is an announced credit, not a seat-price cut. Confirm in the Help Center article before you book it.

    Operator note

    If a loop is pinned to Haiku 4.5, it is still on the $1 / $5 meter. Move it to Haiku 5.5 only if the workload can take the new model and you watch the 100k prompt line. Cursor on-demand that bills Anthropic list will pick up the new SKU when Cursor exposes it. Cursor seat prices did not move with this launch.

    Live desks: API rates · seat tiers · Claude Code vs Cursor.

  • Claude for Ecommerce: What Business Owners Can Actually Do With It (2026)

    Claude for Ecommerce: What Business Owners Can Actually Do With It (2026)

    Claude for ecommerce means using Anthropic’s Claude AI across the jobs around selling online — writing product content, answering customer questions, cleaning up catalog data, and getting your store ready for the AI shopping agents that are starting to buy on customers’ behalf.

    Not hype. Not a robot that runs your store. Just a very capable assistant pointed at the work that eats your week. Here’s what that looks like in practice.

    The Four Lanes

    Every ecommerce use of Claude falls into one of four lanes. Pick the lane with the most pain first.

    1. Product content

    Write and fix product descriptions at scale. Give Claude your specs, your brand voice, and a few examples of descriptions you like. It drafts the rest — titles, bullets, meta descriptions, alt text. The job isn’t “write it for me,” it’s “write the first draft so I’m editing instead of staring at a blank page.”

    Clean your catalog. This is the unsexy one that pays the most. Missing GTINs, inconsistent size formats, half-empty attribute fields — Claude reads a product export and tells you exactly what’s broken, row by row. Clean catalog data is also what AI shopping agents read when they decide whether to recommend your products, so this work compounds.

    2. Customer conversations

    Pre-sale questions. “Does this come in blue?” “Will it arrive by Friday?” “What’s your return policy?” Claude-powered chat answers these from your actual policies and product data — not from a script that breaks the moment someone asks something unexpected.

    Support triage. Claude reads the incoming ticket, pulls the order details, and drafts the response or routes it to the right person with a summary. Your team stops starting from zero on every message.

    Returns and post-purchase. The most common post-purchase questions have known answers. Claude handles them; humans handle the exceptions. That’s the whole model.

    3. Back-office ops

    Supplier and vendor email. Drafting, summarizing threads, pulling action items out of long exchanges. The inbox work nobody wants to do.

    Reporting in plain English. Feed Claude your sales export and ask what changed this week, which products are slipping, and what’s driving the shift. You get the insight without building the dashboard first.

    SOPs and training. Turn “how we do returns” from tribal knowledge into a written process a new hire can actually follow.

    4. Getting agent-ready

    This is the lane most owners are missing. AI shopping agents — built on Claude, among others — are starting to complete purchases on behalf of buyers. They don’t browse your site. They read your structured data: product feeds, schema markup, policies as data.

    Claude helps you become the store agents recommend: auditing your product data for completeness, generating the structured content agents consume, and testing your checkout the way an agent experiences it. The merchants who do this work now get recommended. The ones who don’t get skipped — quietly, by software, at scale.

    What It Costs to Start

    Less than you think. A Claude Pro subscription covers the conversational work — drafting, analysis, inbox help. API usage covers the automated work — catalog cleanup, chat on your site, ticket triage — and it’s metered, so a small store’s bill is small. We’ve got a full breakdown of Claude’s pricing, plans, and limits if you want the numbers.

    The expensive part was never the tool. It’s the hour you spend figuring out where to point it first. Start with one lane, one workflow, one repeatable job. Get that working before you add the second.

    What Claude Won’t Do

    Honest limits, because overselling helps nobody:

    It won’t run your store. Pricing decisions, supplier relationships, and judgment calls stay human. Claude drafts; you decide.

    It needs checking on anything customer-facing. Product descriptions, policy answers, support replies — review before they ship, especially early. The error rate drops as you tune it, but the review habit shouldn’t.

    It doesn’t replace your data. Claude is only as good as what you feed it. Wrong inventory data in, confident wrong answers out. Fix the source data — that’s lane one for a reason.

    Getting Started: The First Week

    Day 1–2: Pick one job. The one you dread most that happens every week. Product descriptions, support replies, inbox triage — one thing.

    Day 3–4: Show Claude how. Give it 3–5 examples of the job done well. Examples beat instructions every time.

    Day 5: Run it supervised. Let Claude do the job, review everything, correct what it gets wrong. The corrections are training.

    Week 2: Loosen the grip. Once the output is consistently right, review spot-checks instead of everything. Add the second job.

    Related Reading


  • Claude Code Cloud Sessions Go GA: Claim Your $100 or $250 Credit by October 7

    Last verified: October 6, 2026 (Pacific).

    Direct answer: Anthropic moved Claude Code cloud sessions from research preview to general availability on September 23, 2026. Existing Pro subscribers can claim a one-time $100 credit and Max subscribers a one-time $250 credit — but only for cloud-session usage, and only if you claim by 11:59 PM Pacific on October 7, 2026. Unclaimed credit disappears. Claimed credit that goes unused expires November 4, 2026.

    What a cloud session actually is

    Claude Code running on Anthropic's machines instead of yours. You hand it a task and a GitHub repository; it keeps working after you close the laptop, lose Wi-Fi, or leave the room. Anthropic's pitch: "Cloud sessions run on Anthropic-hosted infrastructure, so the work keeps going even without your computer running."

    The practical differences from a local session:

    • Your laptop is not the bottleneck. No sleep, no battery, no VPN drop killing a long task.
    • Isolation. The agent works in a hosted environment, not on your machine's files — which limits blast radius.
    • Accessible everywhere. Start on desktop, check on mobile.
    • It draws from credit, not just plan limits. The one-time credit applies automatically when you start a session, and it is separate from your weekly usage limits. Anthropic's framing: "If you hit a limit locally, keep going in the cloud until your credit runs out."

    The credit, precisely

    Pro Max
    One-time credit $100 $250
    Claim deadline 11:59 PM PT, Oct 7, 2026 11:59 PM PT, Oct 7, 2026
    Unused credit expires 11:59 PM PT, Nov 4, 2026 11:59 PM PT, Nov 4, 2026
    Eligibility Individual subscriber active Sept 23, 2026 Individual subscriber active Sept 23, 2026

    One credit per account. The credit covers cloud sessions only — not chat, not API calls, not local Claude Code. It applies before your regular plan usage, and once it's gone, cloud sessions count against your normal plan limits. There is no separate charge for the cloud container itself.

    What you need: a connected GitHub account, because every cloud session works against a repository. No GitHub, no session, no credit use.

    How to claim it

    1. Confirm your plan. Pro or Max, individual subscription, active on September 23.

    2. Connect GitHub. Required before a cloud session will start.

    3. Claim. Open claude.ai/code and use the Claim credit prompt, or run /claim-credit inside the Claude Code CLI.

    4. Start a session. From claude.ai/code, the Code tab in the Claude mobile app, the desktop app, or claude --cloud in the terminal. Anthropic also lists Routines as a starting point.

    5. Watch the dates. Claim by October 7; spend it by November 4. Last call as of today, October 6: the claim window closes 11:59 PM Pacific tomorrow, October 7, 2026. Claim it now — unclaimed credit disappears.

    Team and Enterprise users get cloud-session access through premium seats, but the $100/$250 promotional credit is the Pro/Max subscriber offer — evaluate the feature on its own merits if you're outside the promo.

    Under the hood

    Anthropic runs cloud sessions on fresh Ubuntu 24.04 virtual machines — roughly 4 vCPUs, 16 GB of RAM, 30 GB of disk, per published reports. Organizations that can't let source code run on a vendor's VMs can route sessions to self-hosted environments instead — a separate path from the consumer credit.

    Note the contrast with Remote Control: Remote Control connects a web or mobile interface to a Claude Code session running on *your own computer*, so that machine has to stay awake. Cloud sessions remove the machine entirely.

    Should you use it?

    Treat the credit as a trial budget. Point it at work that's easy to verify: bug fixes with test coverage, dependency updates, questions about a codebase. Check the branch and the pull request the agent produces before merging anything. Anthropic even describes auto-fix of pull requests directly in the cloud as a feature — still check the diff yourself.

    For occasional or non-technical users, be honest with yourself: the credit may go unused, because cloud sessions require a GitHub-connected coding workflow to begin with. That's worth knowing before you count on redeeming the full amount.

  • Claude Sonnet 5.5 Lists at $2 / $10 — Same Unit Price as Sonnet 5

    Last refreshed: October 5, 2026

    Anthropic launched Claude Sonnet 5.5 on September 28, 2026. Seat prices on claude.com did not move. The operator event is a new SKU, not a unit-price cut: Sonnet 5.5 lists at $2 per million input tokens and $10 per million output tokens — the same pair as Sonnet 5.

    Official sources: anthropic.com/claude-sonnet-5-5, platform.claude.com pricing, September 28 rate card, claude.com/pricing.

    What changed

    Sonnet 5.5 is a new SKU, not a rename of Sonnet 5. Anthropic says it runs 30%+ faster than Sonnet 5 and costs up to 30% less per task because it uses fewer tokens, not because the published rate fell.

    Sonnet 5Sonnet 5.5
    Input / MTok$2$2
    Output / MTok$10$10
    5-minute cache write$2.50$2.50
    1-hour cache write$4$4
    Cache read$0.20$0.20
    Batch$1 / $5$1 / $5

    Do not treat “30% less per task” as a 30% list-price cut. The meter is still $2 / $10. US-only inference stays 1.1x on Claude 4.6 and later models.

    What did not change

    Free $0. Pro $20 monthly / $17 annual. Max from $100 (5x) and $200 (20x). Team Standard $20 annual / $25 monthly per seat. Team Premium $100 annual / $125 monthly. Enterprise $20/seat plus usage at API rates. Opus 5.5 remains $4 / $20. Haiku 4.5 remains $1 / $5. Fable 5.1 remains $10 / $50 with $0.25 cache reads. Cursor Individual stays $20; Cursor Teams stays $40/user on cursor.com/pricing.

    Operator note

    If you are pinned to claude-sonnet-5, you are still on the $2 / $10 meter. Switch to claude-sonnet-5-5 if the workload can move and you want the newer model. Cursor on-demand that routes to Anthropic list will pick up the new SKU when Cursor exposes it — Cursor seat prices did not move with this launch.

    Live desks: API rates · seat tiers · Claude Code vs Cursor.

  • Working with the Anthropic API: Console, Models, BYOK & Costs

    Working with the Anthropic API: Console, Models, BYOK & Costs

    Last verified: September 2026. The API is where Claude stops being a chat window and starts being infrastructure. Four deep dives, one hub — the developer console, every model identifier, the subscription-vs-API cost crossover, and the bring-your-own-key strategy that keeps multi-provider stacks from breaking.

    The console: your developer home base

    The Anthropic Console (platform.claude.com) is where the API work actually happens — creating API keys, managing billing, monitoring usage, setting up workspaces, and navigating the developer dashboard. Start here if you haven’t touched the API side yet.

    → Anthropic Console: Developer Quickstart Guide (2026) — API keys, billing, usage monitoring, workspaces.

    The models: every identifier, decoded

    Every current Claude API model string — claude-fable-5, claude-opus-4-8, claude-sonnet-4-6, claude-haiku-4-5 — with context windows, per-token pricing, and when to use each. The one to bookmark; you’ll come back to it every time a new model drops and your code needs the right string.

    → Claude API Models: Complete 2026 Identifier Guide — model strings, context windows, per-token pricing, usage guidance.

    The money question: API vs subscription

    Subscription (Pro/Max) for interactive daily use; API for automation, building, and irregular usage. Here’s the cost crossover — and what the API adds that subscriptions don’t. The honest math on which billing shape fits your workload.

    → Claude API vs Subscription: Which Is Cheaper? (2026) — the cost crossover and what the API adds.

    The multi-provider play: BYOK on OpenRouter

    How to wire bring-your-own-key provider integrations on OpenRouter across dozens of providers without breaking your stack — prioritization, fallback chains, and per-agent configuration. For the builders running more than one model behind their agents.

    → BYOK on OpenRouter: Provider Keys, Prioritization, and Fallback Strategy — provider keys, prioritization, fallback chains.

    Four deep dives, one hub. The console to get set up, the model identifiers to wire it right, the cost math to bill it right, and BYOK when one provider isn’t enough.

  • Claude Code: Setup, Pricing, Limits & Picking Your Dev Tool

    Claude Code: Setup, Pricing, Limits & Picking Your Dev Tool

    Last verified: October 2026. Claude Code is Anthropic's terminal coding tool — it lives where developers live, in the command line. Around it has grown a small universe: install paths, seat pricing, credit pools, rate limits, and three sibling agent surfaces that people constantly confuse with it. This guide is the map.

    Installing it: two minutes, pick your path

    On Windows, it's PowerShell, one command, no Node.js required — the native install path, verified against the May 2026 installer, including the five errors you’ll hit and the exact fix for each. For the general path, it's the one-line npm CLI install plus the Desktop app, done in under two minutes, with the common errors covered.

    → Install Claude Code on Windows: 2026 Step-by-Step — the Windows path: one command, five errors, five fixes.

    → Install Claude Code: Complete Desktop & CLI Setup Guide — the general path: npm one-liner, Desktop app, troubleshooting.

    What it costs: seats, tiers, and the API meter

    Claude Code rides on your existing seat — Pro ($20/month), Max ($100 or $200/month), Team, or Enterprise. The API path is a separate console meter, not drawn from your seat. If you're deciding between Pro and Max for dev work, the question is usage volume: Max is for the people who live in the terminal all day.

    → Claude Code Pricing in 2026: Pro vs Max vs API Costs Explained — seats vs API, verified September 2026, with current token rates on the pricing hub.

    → Claude Code Pricing 2026: Pro, Max, and API Limits — the tier comparison for dev workflows, including Opus 4.7 API rates.

    How the billing actually works: subscriptions vs credit pools

    This is the part that surprises people. Interactive terminal use draws on your Pro/Max subscription — it's part of the seat. But since June 15, 2026, Agent SDK and headless (claude -p) usage moved to separate monthly billing. Same tool, two meters, depending on how you invoke it. Know which one you're on before the invoice teaches you.

    → Claude Code Billing & Monthly Credit Pools (2026) — subscription draw vs separate Agent billing, and how the credit pools work.

    The limits: two clocks

    Claude Code meters two clocks: a rolling 5-hour session window and a weekly bucket. The +50% weekly promo ended September 13, 2026 — what replaced it is a permanent +25% on the weekly limits. Note the model gating: Fable 5.1 is included only on Max and premium seats.

    → Claude Code Limits (September 2026) — both clocks explained, what's permanent, and where Fable 5.1 is available.

    Picking your surface: Cowork vs Code vs Agent SDK vs Managed Agents

    Anthropic now has four agent surfaces and they are not interchangeable: Claude Code, Claude Cowork, the Agent SDK, and Managed Agents. Interactive vs autonomous is the real dividing line — which surface fits depends on who's driving and how much autonomy the job needs.

    → Claude Cowork vs Code vs Agent SDK vs Managed Agents (2026) — the decision matrix: who each surface is for and where each runs.

    Cowork in action: the daily briefing

    The canonical Cowork workflow: connect your calendar, email, and tasks, write the right prompt, and schedule it to run automatically every morning. A briefing that builds itself before you've had coffee. It's the clearest demo of what the non-code surface is for.

    → Claude Cowork: Daily Briefing & Automated Sync (2026) — setup, prompt design, and scheduling.

    Eight deep dives, one hub. Install it, price it, learn the billing and limits, then pick the right surface for the job.

  • We Retired the Living Leaderboard. Date Your AI Comparison Pages.

    We Retired the Living Leaderboard. Date Your AI Comparison Pages.

    Direct answer: a living AI model leaderboard rots. On the public Claude 4.6 vs GPT-5 leaderboard we replaced the promise that standings were “continuously updated by our autonomous tracker” with a September 2026 editor’s note. The table stayed. The date stayed. The page is now a snapshot of the race on 30 May 2026 — not a live scoreboard.

    If an answer engine cites an undated comparison as current, it will be wrong within a release cycle. Date the page. Point prices at a desk you actually re-verify. Leave last season’s Elo alone unless you re-measured it.

    What changed on the public pages

    Three live URLs now say the same thing in different words:

    • Claude 4.6 vs GPT-5: The 2026 Leaderboard — editor’s note that the autonomous tracker retired after the 30 May 2026 update. The LMSYS box still reads Last Updated: 2026-05-30, with Claude 4.6 Sonnet (Elo 1345), GPT-5 Early Preview (Elo 1338), and Claude 4.6 Haiku (Elo 1312). Those numbers were not rewritten this month.
    • Claude 4.6 Roadmap: Guide for Technical Founders — September 2026 editor’s note at the top of the body: the roadmap is a May 2026 generation snapshot. Stop 2 now points at the leaderboard snapshot for where Claude 4.6 stood against GPT-5 in May 2026.
    • Anthropic Slashes Claude 4.6 Haiku API Pricing by 40% — September 2026 outcome note. The phrase “verified Claude pricing page” goes to the live desk at /claude-ai-pricing/, not to a second rate card buried in the old post.

    Titles and slugs did not move. The old URLs are the record.

    Why a “living” leaderboard fails the reader

    Model names, list prices, and context windows moved several times between that May snapshot and late September 2026. The live Claude desk we keep — last verified 23 September 2026 against Anthropic’s own pages — is a different document from a May Elo box. Mixing them on one URL trains both humans and models to treat last season’s table as this week’s answer.

    That is an AEO problem and a GEO problem. Answer engines prefer a short, dated sentence they can lift. Generative engines prefer a page that does not contradict the next page in your cluster. A tracker you cannot staff is worse than a snapshot you labeled.

    The method: snapshot the race, live-link the meter

    1. Put the as-of date in the first screen. “Last Updated: 2026-05-30” in the box. “Editor’s note (September 2026)” above it. Two dates, two jobs: when the numbers were taken, when you admitted they froze.
    2. Do not invent a new leaderboard you did not run. We did not scrape LMSYS tonight. We did not publish a September Elo column. If the measurement is not in the room, the number does not go on the page.
    3. Send current prices to one desk. Token rates and seats live on Claude Pricing (September 2026). The Haiku cut post now points there. A short companion on the 22 September Opus list sits at Claude Opus 5.5 Cuts Token Price 20% — $4 / $20 List. Quote the desk. Do not fork a third table.
    4. Keep the historical URL. Changing the slug of a comparison page that already earned links and citations throws the evidence away. Date the body. Leave the address.
    5. Say what the page is not. A May snapshot is not a buying guide for today’s default model. A 40% Haiku headline from an earlier cycle is not the live list. The pricing desk is the live list.

    What we would not claim

    • We would not claim a September 2026 LMSYS or Arena ranking. We did not pull one for this note.
    • We would not claim Claude 4.6 is still the current default. The live desk names current Opus, Sonnet, Haiku, and Fable lines separately. Read that page for names and rates.
    • We would not restated a full rate card here. Rates move. The desk is dated 23 September 2026 and cites claude.com/pricing and platform.claude.com.
    • We would not describe internal work orders, agents, or edit packets. Those are not the public record. The public record is the three URLs above.

    How to write the editor’s note so an answer engine can use it

    Keep the note to one sentence that answers “is this current?” Then link the current desk.

    Pattern we used: Editor’s note (Month Year): the living tracker was retired after [snapshot date] — the standings below are preserved as a snapshot of the race at that point.

    That sentence is the AEO payload. It is short. It names the freeze date. It tells a model not to treat the table as live. GEO follows if the rest of the cluster agrees: founder roadmap says snapshot, pricing post says “go to the desk,” desk says last verified.

    FAQ

    Q: Should I delete an old model comparison?
    A: No, if the URL already has links or citations. Label it a snapshot, keep the slug, and point current buyers at the live desk.

    Q: When does a snapshot need a new page instead of an editor’s note?
    A: When the question changed. “Where did Claude 4.6 sit vs GPT-5 in May 2026?” is a history question. “What does Claude cost this week?” is a desk question. Different questions get different URLs.

    Q: Can I keep a living tracker?
    A: Only if someone re-measures on a published cadence and the page shows the last run date. A tracker you do not run is a lie with a progress spinner.

    Q: Where are current Claude prices?
    A: tygartmedia.com/claude-ai-pricing/, last verified 23 September 2026 against Anthropic’s public pricing pages. Confirm Anthropic before you quote a customer.

    Q: Does this mean the May Elo numbers were wrong?
    A: It means they are dated. They remain the numbers printed on that page for 30 May 2026. They are not a September 2026 ranking.

    Sources

    • Live pages on tygartmedia.com, read 24 September 2026: leaderboard snapshot, founder roadmap snapshot note, Haiku pricing outcome note, Claude pricing desk (desk last verified 23 September 2026).
    • Official Anthropic seats and API tables linked from the pricing desk: claude.com/pricing and platform.claude.com pricing.

    Related on Tygart Media: May 2026 leaderboard snapshot · founder roadmap snapshot · Haiku pricing note · live Claude pricing desk · Opus 5.5 list-price note · the site has to be the answer.

    I write pages like this so AI search cites a dated sentence instead of last season’s table — then I do the same for operators who publish. That’s what Tygart Media does.

  • Claude Opus 5.5 Cuts Token Price 20% — $4 / $20 List

    Last refreshed: October 6, 2026 (Pacific)

    Anthropic launched Claude Opus 5.5 on September 22, 2026. Seat prices on claude.com did not move. The operator event is the unit price: Opus 5.5 lists at $4 per million input tokens and $20 per million output tokens — 20% below Opus 5 at $5 / $25.

    Official sources: anthropic.com/claude-opus-5-5, platform.claude.com pricing, September 22 rate card, claude.com/pricing.

    What changed

    Opus 5.5 is a new SKU, not a rename of Opus 5. Anthropic says it performs at the level of Fable 5.1 on most work and costs about 40% less than Opus 5 on typical token-billed workloads because cache reads fell more than the headline rate.

    Opus 5Opus 5.5
    Input / MTok$5$4
    Output / MTok$25$20
    5-minute cache write$6.25$5
    1-hour cache write$10$8
    Cache read$0.50$0.20
    Fast mode$10 / $50$8 / $40
    Batch$2.50 / $12.50$2 / $10

    Cache reads on Opus 5.5 are 0.05x input ($0.20), not the 0.1x used on Opus 5. That is the line that moves agent and Claude Code bills. US-only inference stays 1.1x on both SKUs.

    What did not change

    Free $0. Pro $20 monthly / $17 annual. Max from $100 (5x) and $200 (20x). Team Standard $20 annual / $25 monthly per seat. Team Premium $100 annual / $125 monthly. Enterprise $20/seat plus usage at API rates. Sonnet 5.5 remains $2 / $10. Haiku 4.5 remains $1 / $5. Fable 5.1 remains $10 / $50 with $0.25 cache reads.

    Opus 5.5 is available on Pro, Max, Team, and Enterprise. Anthropic also said five-hour usage limits on those plans increased with the launch. Confirm the live window in Settings > Usage. Do not treat a help-center message count as a hard cap.

    Operator note

    If you are pinned to claude-opus-5, you are still on the $5 / $25 meter. Switch to claude-opus-5-5 if the workload can move. Fast mode is first-party Claude API only at $8 / $40. Cursor on-demand that routes to Anthropic list will pick up the new SKU when Cursor exposes it — Cursor seat prices on cursor.com ($20 Individual, $40 Teams) did not move with this launch.

    Live desks: API rates · seat tiers · Claude Code vs Cursor.