Last verified: September 2026. Claude's pricing moves fast — new models, new tiers, new limits every few months. This guide is the map: the direct answer up front, then every deep dive we've published, organized so you can find exactly the piece you need. For today's exact numbers, the linked tracker pages stay current.
The short answer: what does Claude cost?
As of September 2026, Claude's lineup is: Free ($0), Pro ($20/month, or $17/month billed annually), Max (from $100/month), Team (Standard $20–$25/seat/month, Premium $100–$125/seat/month depending on billing, 2–150 seats), and Enterprise (custom, starting around $20/seat/month). API pricing is separate from chat seats — a Pro subscription does not include API credits.
That's the shape of it. Everything below is the detail — pick your question and follow the link.
The plans, side by side
Five tiers, five different buyers. Free is the trial. Pro is the individual power user. Max is for people who live in Claude all day. Team is per-seat collaboration with admin controls. Enterprise is custom contracts with security review.
This is where buyers get confused, because the two seat types look similar and cost very differently. Standard seats run roughly $20–$25 per seat per month; Premium seats run roughly $100–$125. The difference is usage allowance and admin controls — Premium is for the people on your team who burn through a Standard seat's limits by lunch.
Rate limits and usage limits: the frustration chapter
Rate limits are the number-one Claude complaint, and the number-one thing buyers underestimate. Every plan has them, they differ between chat and API, and Team plan limits doubled in May 2026 after Anthropic's compute deal with SpaceX's Colossus 1 — except the Free plan, which was left out.
Token limits and context windows, in plain English
Context window is how much Claude can hold in its head at once; output limit is how much it can write in one response. As of late 2026: Fable 5, Opus 4.8, and Sonnet 4.6 carry a 1M-token context window; Haiku 4.5 carries 200K. Maximum output runs to 128K tokens on the big models. In practice: 1M tokens is roughly a shelf of books in one conversation.
Three model families, three jobs. Haiku is fast and cheap — the one you call a thousand times a day. Sonnet is the daily default, the balance of smarts and speed. Opus is the flagship — the one you reach for when the problem is hard and the answer matters. Fable sits above them as the current top-tier model.
What's current: the model tracker and release history
The lineup as of September 8, 2026: Fable 5.1 (top), Opus 5 (flagship daily driver, Max default), Sonnet 5 (Free/Pro default), Haiku 4.5 (fast). Recent history: Fable 5.1 and Mythos 5.1 landed September 1, Opus 5 on July 24, Sonnet 5 on June 30, Fable 5 on June 9.
Two doors into Claude: the chat app (claude.ai) and the API (console.anthropic.com). Getting an API key takes about five minutes — create an account, add a payment method, generate the key. The Console is also where you watch your API spend burn, which you should do early and often.
The honest answer first: there is no public Claude Pro student coupon. The student path runs through partner universities — free premium access via your school email through Claude for Education. Note the naming trap: “Claude for Teachers” is the K-12 program, not the campus one.
Anthropic's pricing makes more sense once you know the company's shape — an AI research company whose compute deals (like the SpaceX Colossus 1 agreement) directly move what you pay.
This guide links thirteen deep dives, all verified against September 2026 pricing. Claude's lineup changes fast — when in doubt, the pricing tracker and model tracker carry the current numbers.
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.
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
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.
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.
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.
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).
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.
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.
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 5
Opus 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 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.
The live Anthropic platform table lists Claude Sonnet 5 at $2 input / $10 output per million tokens. Five-minute cache writes are $2.50. Cache reads are $0.20. Batch is $1 / $5.
That is not Sonnet 4.6. Sonnet 4.6 (and Sonnet 4.5) stay at $3 / $15. Do not average the two rows.
On September 17 this desk published that Sonnet 5 intro $2 / $10 had ended August 31 and that standard list was $3 / $15. The official table on September 22 does not match that desk. Official page wins. Old → new on the live pages: Sonnet 5 $3 / $15 → $2 / $10.
Seats did not move: Pro $20 monthly / $17 annual, Max 5x $100, Max 20x $200, Team Standard $20 annual / $25 monthly, Team Premium $100 annual / $125 monthly, Enterprise $20/seat plus API usage.
Fable 5.1 remains $10 / $50 with cache reads at $0.25 (already logged September 19). Cursor individual seats remain Hobby free / Pro $20 / Pro+ $60 / Ultra $200.
Updated in place: the four canonical pricing desks plus the Claude Code vs Cursor page.
Last verified: September 18, 2026 (Pacific Time). The June 2026 edition covered the Fable 5 public launch, the June 15 model retirements, and Managed Agents self-hosted sandboxes.
Direct Answer (September 2026 Update): September’s biggest move is economic, not a new flagship: Claude Fable 5.1 (released September 1) cuts cache-read pricing 75%, which Anthropic says makes typical workloads about 25% cheaper. The same day brought the restricted-access Mythos 5.1 and Enterprise Frontier Safeguards. Mid-month, Anthropic shipped vertical plugins for financial advisors (Sept 14) and a major small-business expansion (Sept 15), then folded Cowork into a single Claude experience with Docs and Slides in beta (Sept 16).
September 2026 is Anthropic’s enterprise-monetization month: no new flagship tier, but cheaper agentic workloads, a compliance-ready data story, and the product surface consolidating around one Claude. Here is everything dated, with the numbers and the migration notes.
Claude Fable 5.1 and Mythos 5.1 — cache reads cut 75% (September 1, 2026)
Anthropic released Claude Fable 5.1 on September 1, 2026, alongside Claude Mythos 5.1. The two are the same underlying model at different safeguard tiers: Fable 5.1 is generally available; Mythos 5.1 is restricted to vetted organizations through Anthropic’s Project Glasswing trusted-access program, initially in cybersecurity and life-sciences work.
The headline is pricing, not capability. Base rates are unchanged — $10 per million input tokens, $50 per million output — but cache reads fall from $1.00 to $0.25 per million tokens, a 75% cut. Anthropic’s own estimate: typical workloads get ~25% cheaper, highly agentic ones up to 45%. Treat those as vendor math — the savings scale entirely with how cache-heavy your workload is.
The practical details:
Model ID:claude-fable-5-1
Context window: 1M tokens; max output 128K
Benchmarks: 52.6% on Terminal-Bench-Science 0.1 (vs 24.7% for Fable 5); 42% → 55.8% on Terminal-Bench 4.0
Safeguard friction down: ~60% fewer cybersecurity false positives per Claude Code session; 85% fewer interventions on benign biology and medical requests. Fable 5.1 can identify software vulnerabilities but blocks penetration testing, exploit generation, and binary-based vulnerability scanning
Availability: Claude API, Amazon Bedrock, Google Cloud Vertex AI, Microsoft Foundry, and the Claude app
Migration is not a string swap: breaking changes include forced tool use, thinking blocks, and edited conversation histories. Prefix-binding enforcement began August 31 for newly created API accounts. Anthropic’s stated retirement horizon: no earlier than September 1, 2027
Claude Code 2.1.257 makes Fable 5.1 the default Fable model (gateway aliases excepted)
Enterprise Frontier Safeguards — phased rollout through fall 2026
Alongside the models, Anthropic announced Enterprise Frontier Safeguards (EFS), a new security architecture that lets organizations keep monitoring data inside infrastructure they control, with zero-retention options for Fable 5 and 5.1. The company acknowledged that Fable 5’s 30-day data-retention requirement had limited adoption by regulated enterprises — EFS is the answer, rolling out in phases through fall 2026. For healthcare, finance, and legal buyers, this is the compliance unlock that makes the cheaper agentic workloads actually purchasable.
On September 2, Anthropic opened a limited-access API that detects invisible watermarks in Claude-generated text. Access is restricted to organizations with a verification mandate — newsrooms, regulators, independent researchers, professional fact-checkers. Regular users and companies embedding Claude don’t get it. The design is deliberate: it gives watchdogs a provenance tool while limiting adversarial probing of the signal.
Fable 5.1 lands on Claude for Government (September 9, 2026)
Teresa Carlson, Anthropic’s global head of public sector, announced at the Billington Cybersecurity Summit on September 9 that Fable 5.1 is now available on Claude for Government, the company’s FedRAMP High-authorized platform — meaning any agency requiring FedRAMP High can use it. AWS had made the model available in its US government cloud the prior week. Carlson signaled more government-focused releases in the coming weeks.
Claude for Financial Advisors (September 14, 2026)
Anthropic released Claude for Financial Advisors, a plugin bundling connectors to custodians, asset managers, and wealth-tech providers with workflow skills built around an advisor’s day. It’s available to Enterprise customers through the Cowork plugin browser. Connectors include Charles Schwab, BlackRock, Addepar, Envestnet, iCapital, Orion, SS&C Black Diamond, Wealthbox, Wealth.com, Vanguard, and Zocks — alongside existing Microsoft 365, Salesforce, DocuSign, Box, FactSet, S&P Global, and Morningstar integrations. Packaged skills cover advisor onboarding, alternative-investments briefing, compliance and AI-policy review, estate and tax briefing, portfolio-rebalance review, post-meeting notes and follow-up, pre-meeting preparation, and prospect intake. The pattern matches June’s legal vertical bundle: Anthropic is shipping industry-specific integration packs instead of leaving the ecosystem to build them.
Claude for Small Business: 43 workflows, 27 integrations (September 15, 2026)
Anthropic expanded Claude for Small Business on September 15, growing the plugin to 43 workflows and adding 27 integrations including Shopify, Salesforce, TikTok, Atlassian, Zoom, Xero, Gusto, Square, Stripe, and Zapier. It runs inside Claude Cowork: owners install the plugin, run /smb-onboard, connect their tools, and pick a task. Every workflow starts in approval mode — Claude drafts and stages the work, then waits for the owner’s approval before anything sends, posts, or pays — and owners can flip a single workflow to autonomous and back. Example workflows: a Monday brief assembling cash position, week-over-week sales, pipeline movement, overdue invoices, and the three things needing the owner; inbound-lead response; branded proposals priced from past jobs; staged marketing campaigns; month-end close. The plugin is available on every paid Claude plan; Anthropic recommends the Team plan for businesses with more than one person. A fall schedule of free in-person workshops, partner webinars, and community-run training ships with it.
One Claude: Cowork folds in, Docs and Slides launch in beta (September 16, 2026)
Anthropic announced September 16 that Claude Cowork and Claude chat are merging into a single Claude, rolling out to Pro and Max plans over the coming weeks. No mode to choose: users describe what they need, and Claude decides whether to answer directly or take on the bigger job — research, reports, spreadsheets, presentations — handing back finished, editable files. Two new tools launch in beta for paid users: Claude Docs (create and edit documents inside a conversation) and Claude Slides (generate presentations — editable, downloadable as PowerPoint or PDF, exportable to Google Docs or Microsoft Word, with shareable links across desktop and mobile). Anthropic’s stated reason: users found it frustrating to decide where a task belonged, since work started in one product didn’t carry into the other. The Cowork arc that led here: research preview for Max on macOS (January 12), Pro (January 16), general availability on macOS and Windows (April 9), web and mobile (July 7), memory shared across chat and Cowork in the cloud (August 25).
Current Claude model lineup and API pricing (September 2026)
Model
Input $/1M
Output $/1M
Cache read
Fable 5.1
$10
$50
$0.25
Opus 5
$5
$25
$0.50
Sonnet 5
$2
$10
$0.20
Haiku 4.5
$1
$5
$0.10
5-minute cache writes are 1.25× base input; 1-hour writes are 2×. Batch API is 50% off input and output. Full table and seat pricing live on our Claude AI pricing guide.
What to watch for in October
One-Claude rollout: the unified experience continues rolling out to Pro and Max; Docs and Slides are still in beta — watch for GA and Team/Enterprise availability.
Enterprise Frontier Safeguards: phased rollout continues through fall 2026; the zero-retention option is the milestone regulated buyers are waiting on.
Government releases: more Claude for Government announcements were telegraphed for the coming weeks.
IPO watch (reported, not confirmed): Bloomberg and Fortune reporting positions Anthropic for an October 2026 public offering. No official date — treat as rumor until the filing.
Live, vendor-neutral prices & limits for ChatGPT, Claude, Gemini, Perplexity and more — and we’ll email you the moment your tools change price or limits. Free, no hype. See our live AI model tracker.
Sonnet 5 is no longer $2 / $10 on the first-party API table. Anthropic published introductory pricing through August 31, 2026, then the standard rate: $3 per million input tokens and $15 per million output tokens starting September 1, 2026.
That is a 50% unit-price move on input and output versus the intro card. Sonnet 4.6 was already $3 / $15. The two mid-tier SKUs now share the same list. Cache writes follow the new input rate ($3.75 / MTok for 5-minute writes; $0.30 / MTok cache reads). Batch stays 50% off that list.
What did not move on this check:
Claude Pro $20/mo or $17/mo annual ($200 prepaid)
Max 5x $100/mo, Max 20x $200/mo
Team Standard $25 monthly / $20 annual; Premium $125 / $100
Haiku 4.5 $1 / $5; Opus family $5 / $25; Fable 5 $10 / $50
Lineup currency (Sept 2026): Current API list (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 on Anthropic’s card): Opus 4.8 $5/$25, Sonnet 4.6 $3/$15.
Cursor Hobby free, Pro $20, Pro+ $60, Ultra $200, Teams $40/user
If a workflow was budgeted on Sonnet 5 intro rates, the meter is now the same as Sonnet 4.6. Haiku 4.5 is still the cheap public list. Live desks: API rates, seats.
Direct answer (23 September 2026): Claude chat usage is not a fixed message count and not an API credit balance. claude.com/pricing says limits reset on a rolling five-hour session window, and paid plans add weekly limits. Pro is at least 5× Free per five-hour session. Max is 5× or 20× Pro per five-hour session. Team Standard is 1.25× Pro per session and Team Premium is 6.25× Pro per session (Help Center Team article, read 23 September 2026). File and image ceilings are separate from that meter. The error strings below were already on this page; they were not re-read from Anthropic docs on 23 September 2026. Confirm current seat prices on Claude AI Pricing.
This page is the limits and errors desk. It does not restate list prices. Official plan names and token rates live on the pricing slug. Current model names live on the model tracker.
Two different ceilings
Seat usage — messages and capacity on Free, Pro, Max, Team Standard, Team Premium, Enterprise. Extra usage on paid chat, when enabled, bills at API rates.
Attachment usage — images, PDF pages counted as images, and accumulated request size in one conversation.
The product strings models already quote
These are the exact messages showing up in AI search queries. Treat them as product copy, not as Tygart inventions.
“You’ve reached the limit for chats that include files or images. Start a new text-only chat or upgrade to continue now.”
“Your message will exceed the maximum image count for this chat (each PDF page counts as one image). Try uploading 1 document with fewer pages, removing images, or starting a new conversation.”
“This chat has reached the 100-image limit (including PDF pages). Start a new chat to add more.”
“Request too large (max 32MB). Accumulated images and attachments in the conversation pushed the request over the limit. Run /compact, or double press Esc to go back and remove attachments.”
“Failed to start Claude’s workspace. Not enough disk space to set up the workspace.” Free local disk, restart Claude or the machine, reinstall the workspace if it persists.
“Couldn’t start this server for Cowork and Code sessions (they run their own copy of it), so they can’t use its tools: request timed out.” See Cowork not working.
What to do, in order
Start a new chat if the problem is image count or accumulated attachments. PDF pages count as images.
Run /compact or strip attachments if the request crossed 32MB.
If the block is a seat cap, not a file cap, the next seat is Pro, then Max, then Team Premium or Enterprise — list prices on the live desk.
API workloads do not use this chat meter. Keys and prepaid credits live in the Anthropic Console.
Last verified: September 23, 2026 (Pacific). API figures from xAI developer pricing and Anthropic model cards. Consumer seat prices vary by store and region — confirm at x.ai and claude.com before you pay.
Direct answer: Grok is cheaper per token at every comparable rung. Claude is cheaper only if you stay on Sonnet 5 ($2/$10) or Haiku 4.5 ($1/$5) and never call Fable. Consumer stickers look inverted: Claude Pro is $20, SuperGrok is about $30. The catch is what the seat includes. Pro does not include Fable. Max includes Fable only up to 50% of the weekly pool. Grok has no public $10/$50 SKU.
Consumer seats
Grok (xAI)
Claude (Anthropic)
Free
Metered on grok.com and X
Metered, Sonnet
Everyday paid
SuperGrok ~$30/mo (X Premium+ bundle ~$40)
Pro $20/mo
Heavy individual
Plus ~$100 or Heavy ~$300
Max 5x $100 / Max 20x $200
Team
Grok Business ~$30/seat
Team ~$20-25/seat annual
Claude Pro wins the $20 vs $30 sticker. Max 20x ($200) undercuts SuperGrok Heavy ($300). They are not the same product: Claude splits models by plan. Fable 5 / 5.1 is included on Max and premium Team/Enterprise seats only, capped at half the weekly bar. Pro and Team Standard pay usage credits from the first Fable token. Details: Fable pricing and plan access and Claude Code limits (Sep 2026).
API rates per million tokens
Grok. Official xAI card. Prompts that reach 200k tokens are billed at 2x for the whole request.
Model
In / out
Context
Cached input
Grok Build 0.1
$1 / $2
256k
$0.20
Grok 4.3 / 4.20
$1.25 / $2.50
1M
$0.20
Grok 4.5 / 4.6
$2 / $6
500k
$0.30-$0.50
Claude.
Model
In / out
Context
Cache read
Haiku 4.5
$1 / $5
200k
$0.10
Sonnet 5
$2 / $10
1M
$0.20
Opus 5.5 (current)
$4 / $20
1M
$0.20
Opus 5 (legacy)
$5 / $25
1M
$0.50
Fable 5.1
$10 / $50
1M
$0.25
Fable 5.1 headline rates match Fable 5. The Sep 1 change was cache reads: $1.00 to $0.25. A cold Fable call is still the expensive product.
Same-class pairing
Everyday production: Grok 4.3 ($1.25/$2.50) vs Sonnet 5 ($2/$10). Grok is cheaper, especially on output.
Flagship work: Grok 4.6 ($2/$6) vs Opus 5.5 ($4/$20). Grok still cheaper on list. (Legacy Opus 5 remains $5/$25.)
Top shelf: Grok has no $10/$50 public model. Fable 5.1 is 5x Grok 4.6 input and about 8x output.
Worked example
10M input + 2M output, no cache, short prompts:
Grok 4.6: $20 + $12 = $32
Sonnet 5: $20 + $20 = $40
Opus 5.5: $40 + $40 = $80
Opus 5 (legacy): $50 + $50 = $100
Fable 5.1: $100 + $100 = $200
Batch: Claude 50% off on supported models. Grok 20% off on 4.3 / 4.20 only – not on 4.5 / 4.6.
Rules that are not the rate card
Claude subscriptions use two clocks: a rolling 5-hour session and a weekly bucket. Claude Code’s temporary +50% weekly promo ended September 13, 2026 at 11:59 PM PT. Starting September 14, 2026, Help Center (article 15910845): weekly Claude Code limits are permanently 25% higher than the pre-promotion baseline for Pro, Max, Team, and seat-based Enterprise. The 5-hour window does not change.
Grok API doubles the request once the prompt hits 200k tokens. Current Claude Sonnet / Opus / Fable cards do not use that surcharge.
Cache is the only place Fable 5.1 looks cheap at the top. Reused prefixes at $0.25/MTok. Fresh prompts at $10/$50.
When to buy which
Buy Grok for volume, agents, or coding at $2/$6 where Grok 4.6 is enough.
Buy Claude when the job needs Fable-class long horizon and you will pay for it – or when Sonnet 5 at $2/$10 is enough and the team already lives in Claude Code.
Do not pick from the consumer sticker alone. A $20 Claude Pro seat that immediately burns Fable credits can cost more than a $30 SuperGrok seat that never leaves Grok 4.6.
FAQ
Is SuperGrok cheaper than Claude Pro? No on the monthly line: Pro is $20, SuperGrok is about $30. Yes on many API workloads, because Grok 4.6 undercuts current Claude flagship Opus 5.5 ($4/$20) and Fable 5.1 by a wide margin.
Is Claude always more expensive on the API? No. Haiku 4.5 and Sonnet 5 sit near Grok Build / Grok 4.3. The Claude premium starts at Opus 5.5 ($4/$20; legacy Opus 5 $5/$25) and jumps again at Fable.
Does Claude Pro include Fable 5.1? No. Credits from the first token. Included Fable is Max and premium seats, 50% of weekly limits. See Fable plan access.
If you run a restoration or multi-site operation and want the same kind of defensible, versioned standard for your Scope 3 emissions data, see the Restoration Carbon Protocol – the open framework that maps contractor emissions onto the GHG Protocol so commercial clients can actually verify them.
Direct Answer (9 September 2026):Claude for Teachers is the U.S. K-12 product (announced 28 August 2026). Claude for Education is the university program. A .edu login is not a Teachers seat. Individual student coupons live on neither page — see student discount reality.
68% of U.S. Google searches end without a click in 2026. When AI Overviews appear, that rate hits 83%. The question for content-driven businesses is no longer how to rank — it’s how to be cited inside the answer that replaced the click.
This is a practical guide to structuring content, managing brand entity signals, and measuring visibility in a world where users get their answer before they ever reach your site.
What Zero-Click Actually Means for Content Businesses
What zero-click actually means for content businesses.
Zero-click doesn’t mean zero value. Brands cited inside AI Overviews earn 35% more organic clicks than uncited brands on the same query. The traffic goes to the cited brand — not to the site that ranks #1 but isn’t cited.
The data that reframes zero-click as a competition problem, not a traffic problem:
68% of U.S. Google searches are zero-click in 2026 (SparkToro/Similarweb)
When AI Overviews appear, zero-click rate hits 83%
Organic CTR for position #1 drops up to 58% when AI Overviews are present (Ahrefs, December 2025)
Brands cited in AI Overviews earn 35% more organic clicks and 91% more paid clicks versus uncited brands
AI-referred visitors convert at 4.4x the rate of traditional organic visitors (Semrush)
The overlap between top-10 rankings and AI Overview citations: 17–38% in early 2026, down from 75% in mid-2025
The conclusion: ranking is no longer sufficient for visibility. A site can rank #1 and not be cited in the AI Overview that answers the query. The two need to be optimized separately.
How AI Overviews Decide What to Cite
How AI overviews decide what to cite.
Google’s AI Overview system retrieves web pages in real time, synthesizes a 3–5 sentence answer, and cites 3–6 source pages. The selection criteria weight answer extractability, entity authority, freshness, and structured data — not just ranking position.
The signals that influence AI Overview citation:
Answer extractability: The answer to the query must appear in the first 200 words of the page, stated directly. Pages that build toward the answer, providing extensive context before the conclusion, are retrieved for topic relevance but can’t be cited because the extractable answer isn’t there.
Entity authority: Consistent, factually accurate information about the brand entity across the web — site, LinkedIn, social profiles, third-party mentions — signals that the source is authoritative on the topic. AI systems treat entities with strong external corroboration as more trustworthy.
Freshness: For fast-changing topics (Claude pricing, AI model capabilities, regulatory changes), recency is a significant weight. A page last updated in 2024 competes poorly against one updated in August 2026 on a query about current Claude pricing.
Structured data: FAQPage, HowTo, and Article schema markup signals to Google that content is formatted for extraction. Pages with properly implemented schema see measurably higher AI Overview inclusion.
E-E-A-T signals: Experience, expertise, authoritativeness, trustworthiness. An article written by a named author with a consistent byline and external presence outperforms anonymous content on contested or technical topics.
Strategy 1: Structure Every Page for Extraction
Structure every page for extraction.
Answer-first structure is the single highest-leverage change for AI citation rates. The first paragraph of every article should directly and completely answer the likely query.
The structure AI systems can extract from:
H1: [Specific, query-answering title]
[Bold one-sentence direct answer to the query implied by the title]
[Supporting detail — the why, the how, the context]
H2: [First subtopic as a question]
[Bold answer sentence to the H2 question]
[Elaboration]
What this means in practice for tygartmedia.com content:
Every article about Claude pricing, model capabilities, or Anthropic history should open with the factual answer — not a framing sentence, not background, not “in this article we’ll cover.” The answer, stated directly, in the first two sentences.
The reason this matters beyond GEO: it’s also better for users. Answer-first structure is a discipline that makes content more useful and more likely to be cited. The SEO and GEO benefits are secondary to the writing quality improvement.
Strategy 2: Build and Maintain the Brand Entity
AI systems treat brands as entities — named things with verifiable, consistent information across multiple authoritative sources. Building entity authority means making sure that information is consistent, correct, and present everywhere crawlers look.
Entity checklist for tygartmedia.com:
On-site signals:
Organization schema on every page (name, URL, description, logo, founder, sameAs links)
Consistent author byline (“Will Tygart”) on every article
Author bio that establishes expertise consistently across all articles
Contact and about page with complete, factual business information
Off-site signals:
LinkedIn Company Page with consistent description matching the website
Google Business Profile (if applicable) with consistent NAP (name, address, phone)
Third-party mentions and citations on authoritative sites in the AI/tech space
Social profiles with consistent handles and descriptions
The consistency requirement: AI systems cross-reference. If the description on LinkedIn says “AI infrastructure for operators” and the website says something different, that inconsistency weakens the entity signal. Everything should say the same thing about the same thing.
Strategy 3: Implement Structured Data
FAQPage, Article, and Organization schema markup signals to AI Overviews that content is formatted for extraction. This is not optional in 2026 for sites that depend on search visibility.
Minimum structured data implementation:
FAQPage schema on every article with a FAQ section:
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [{
"@type": "Question",
"name": "What is Metricool pricing?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Metricool has a free plan and paid plans starting at the Starter tier. API access requires the Advanced plan or above. Pricing is per brand, not per connected social account."
}
}]
}
Article schema on all editorial content (author, published date, modified date, headline).
In Rank Math (the plugin on tygartmedia.com): FAQ blocks in the WordPress editor generate FAQPage schema automatically. Use the Rank Math FAQ block for all FAQ sections rather than plain text. Article schema is enabled site-wide in Rank Math settings.
Strategy 4: Keep Content Current
AI retrieval systems weight freshness heavily for fast-changing topics. For any site publishing Claude pricing, model capabilities, or AI tool features, stale content is not just less useful — it actively loses citation ground to fresher sources.
Freshness implementation:
“Last refreshed” date at the top of every article — visible to users and read by crawlers as a freshness signal
“What’s new” section in evergreen articles covering frequently updated topics (Claude pricing, model capabilities, Metricool features)
Update the modified date in Article schema whenever content is refreshed — not just the publication date
Monitor Search Console for queries where the site appears in AI Overviews — freshness issues show up as drops in citation before they show up as ranking drops
Trigger list for mandatory refreshes on tygartmedia.com:
Any Anthropic pricing change
Any new Claude model release or deprecation
Any Metricool feature update
Any change to Anthropic’s Enterprise product structure
Strategy 5: Earn Third-Party Citations
AI systems give extra weight to content cited by other authoritative sources. Being linked to or mentioned by other sites publishing on Claude, Anthropic, and AI infrastructure strengthens the entity signals for all related queries.
Practical approaches:
Original data and research: Content with specific numbers, benchmarks, and original findings gets cited by others. The Claude pricing breakdowns, benchmark comparisons, and API cost calculations on tygartmedia.com are exactly the type of content other AI publications cite.
First-mover coverage: Publishing accurate, detailed coverage of Anthropic announcements before or alongside other publications builds a citation pattern over time.
Expertise-signal content: Content that can only be written from operational experience — running 24 brands in Metricool, building vector DB systems for business documents — earns citations because it’s not replicable from Anthropic’s documentation alone.
Measuring Zero-Click Performance
Standard click and session metrics are insufficient for measuring zero-click visibility. The right metrics are AI citation rate, branded search volume trend, and AI-referred conversion rate.
Measurement framework:
Metric
Tool
What It Measures
AI Overview appearances
Google Search Console (AIO report)
Queries where site is cited
CTR on AIO queries
GSC, filter by AI Overview queries
Whether citations drive clicks
AI-referred traffic
GA4 source filter (ChatGPT, Perplexity)
Direct traffic from AI citations
Branded search volume
GSC, filter by brand terms
Awareness from zero-click exposure
Conversion rate from AI sources
GA4 segmented by source
Value of AI citation traffic
Manual testing protocol: Monthly, ask ChatGPT, Perplexity, and Claude the questions your audience asks — “what is Claude Enterprise pricing,” “how does Metricool API work,” “what is the history of Anthropic” — and record whether tygartmedia.com is cited. This is the most direct feedback loop available and costs nothing.
If branded search volume is growing while organic clicks are flat or declining, the site is appearing in AI summaries and building awareness without receiving credit in standard traffic metrics. That’s the zero-click pattern working in favor of the brand — and the signal that citation strategy is working.
Frequently Asked Questions
What is zero-click search?
Zero-click search is a search that ends on the results page itself — the user gets their answer from an AI Overview, featured snippet, or knowledge panel and doesn’t click through to any website. In 2026, 68% of U.S. Google searches are zero-click.
Does zero-click hurt all websites equally?
No. Sites cited inside AI Overviews and featured snippets earn 35% more organic clicks than uncited sites on the same query. Zero-click hurts uncited sites and benefits cited ones. The competition shifts from ranking to citation.
What is the difference between GEO and zero-click optimization?
GEO (Generative Engine Optimization) is the discipline of getting cited inside AI-generated answers from ChatGPT, Perplexity, Gemini, and Claude. Zero-click optimization is specifically about Google search — being cited in AI Overviews and featured snippets. They use the same underlying tactics (answer-first structure, entity signals, structured data, freshness) applied to different surfaces.
How long does it take to see results from zero-click optimization?
Plan for 3–6 months of consistent effort before citation rates change meaningfully. AI systems update their citation patterns as they re-index updated content. The fastest wins come from freshness updates on existing high-traffic pages and FAQ schema implementation on pages that already rank.
Do clicks from AI citations convert differently?
Yes — significantly. AI search visitors convert at approximately 4.4x the rate of traditional organic visitors (Semrush). The mechanism is intent: users who get a specific answer from an AI Overview and then click through to the cited source are further along in their decision process than typical organic visitors.