That is what happened when we pointed a Grok Heavy team at Restoration Intel and told it to ship ten pages. The models were fine. The CMS was fine. The coordination model was not.
This is the write-up of what broke, the rule we kept, and the official doors to walk through if you want the primary sources instead of a recap of a recap.
What the lock actually was
Grok, Harper, Benjamin, and Lucas all had the same WordPress tools: create, update, publish, SEO. When the job got large — ten pages, one Fluent Form, one Rank Math backend — they piled onto the same post IDs.
The connector started returning “another agent already completed this task.” Full-body writes timed out. Rank Math accepted a robots write and then displayed the last token in the array. Live HTML and the sitemap were the only source of truth.
WordPress did not fail as a CMS. Shared write access failed as an operating system.
The rule we kept
Many readers. One writer.
One agent commits. The others draft, QC live URLs, check the form, and stay off the write tools. Humans still own the one-way doors: money, OAuth, and policy.
Prove the capture form before you scale the pages.
Serialize writes. One ID. Wait. Confirm slug, form, word count. Then the next ID.
Do not trust the connector’s SEO GET. Read the live robots tag and the sitemap.
When the tool says another agent finished the call, stop retrying the same payload. Read first.
QC is not writing with extra steps. Drafts can be parallel. Commits cannot.
That is the same pattern as two estimators opening the same job file. Speed without a single owner is not speed. It is a collision.
The second lesson is source hygiene. Threads, screenshots, and “someone said” posts are downstream. Official product pages, docs, and consoles are upstream. Start there. Then decide what the recap is worth.
Corporate structure around these companies moves. This list is a map of official destinations, not a cap table. If a URL 404s, go to the company root and walk the nav. Do not stay on a summary card.
Official xAI / Grok
xAI is the lab. Grok is the product. The docs site is branded SpaceXAI Docs in places. Use the domains below, not a third-party mirror.
Inference base URL from the official docs: https://api.x.ai. Management API: https://management-api.x.ai. Keys live in the console, not in a tweet screenshot.
Official SpaceX, Tesla, X, Neuralink, Boring Company
If you need the source of record for a launch, a car, a post, an implant trial, or a tunnel, these are the front doors.
Starlink is a SpaceX product, not a separate public company. X is the public square. Announcements often land there first. Product facts still have to survive the company site and the docs.
How to use the list
Open the official domain.
If you are building, open docs and the console next.
Treat X as a timestamp, not a spec.
If two recaps disagree, the docs page wins.
That is swimming upstream. The lock taught us to serialize writes. The source list is the same idea applied to information.
Will Tygart — Tygart Media. We write about what we do, including what breaks.
Last verified: 5 September 2026. Practitioner essay from the workbench — not a SpaceX press release. We use this stack because it makes our company better, and we want SpaceXAI, SpaceX, Cursor, X, and Tesla to keep shipping. No affiliate links. Just the tools and the receipt.
This morning I posted a theory I had been living inside for weeks.
They bought Cursor to teach vibe coders how to use SpaceX AI and Grok Bot to teach those who can’t use Cursor. Then you realize Cursor Ultra isn’t needed and that your Grok Super Heavy subscription is the end result. They’re literally building on-ramps and scaffolding to upskill all of the folks they’re going to need in the next 36 months to leap technology forward at an unbelievable rate. Get in the ship.
That post is a reading from the workbench, not official copy. I write it as someone who already treats Cursor as a lead seat, Grok Bot as a Chief of Staff, Notion as the board, and Slack as the doorbell. I have walked WordPress sites by voice. I have rehearsed swarms on a laptop so I would not burn cloud tokens on a pattern that dies in alpha. I have watched Cursor write a work order with Owner = Chief of Staff and watched the Bot pick it up the same way a person would.
The ladder is real. The pedagogy is not documented. The payroll is missing.
What follows separates three things that keep getting smashed together: what SpaceX / SpaceXAI / Cursor actually built and said; the human-node invitation that builders can choose; and the contribution economy that does not exist yet, even though the first two rails of it are already on the floor.
What the company actually assembled
The documented sequence is short and expensive. Official language is consistent: build “the world’s most useful AI models,” combine Cursor’s product and distribution to expert software engineers with Colossus compute, start in software engineering, expand into knowledge work. That is vertical integration, not a secret apprenticeship.
Date
What actually happened
Feb 2026
SpaceX absorbs xAI. The AI work later brands as SpaceXAI.
21 Apr 2026
Partnership with Cursor: option to buy for $60B or pay $10B to work together.
Mid-Jun 2026
Record SpaceX IPO. On 16 Jun the option is exercised. All-stock. Implied Cursor equity value: $60B. Joint model slated for Cursor and Grok Build.
11 Aug 2026
Grok Bot early beta: persistent cloud computers, browser / filesystem / terminal, multi-bot coordination. Official line: “AI teammates you can give real work to.”
14 Aug 2026
Acquisition closes. Cursor’s close post: help make Grok useful and improve Grok Build, Grok Bot, the Grok API, and Cursor.
21–26 Aug 2026
Bot access expands down the plan ladder. Bot usage is separate from Grok and Cursor token pools. Still no standalone Grok Bot SKU.
Company events, not my theory. Verify prices on the live billing pages before you spend.
Rockets and satellites plus X plus Grok plus Colossus plus the application layer where developers already live plus an agent that finishes jobs in existing tools. Buy the surface. Feed the data back into the models. Sell enterprise AI into a market SpaceX described, in IPO materials, as enormous. Catch Anthropic’s Claude Code and OpenAI’s Codex.
That is enough. It is also not the story I told on X.
What they did not say
I have not found, in filings, product posts, or close announcements, any of the following:
That SpaceX bought Cursor in order to teach vibe coders how to use SpaceX AI.
That Grok Bot exists in order to teach people who cannot use Cursor.
A 36-month coordinated workforce-upskilling campaign.
SuperGrok Heavy as the official terminal subscription of that campaign.
An official paid creator commons for community builders.
“Get in the ship” as recruiting copy.
Those lines are mine. Treat them as interpretation or do not treat them at all. The company incentive, on the paper it publishes, is models, data, subscriptions, and distribution. Human capability is a side effect unless someone designs for it.
There is a second tension the marketing does not resolve. Grok Bot is sold as teammates that finish work, not as tutors. The same stack that lowers the skill floor can also replace the person who used to occupy it. That is not a smear. It is the product. We still want the product to succeed, because the alternative is standing still while the floor moves.
Cursor is the AI coding environment that made “vibe coding” a working method instead of a joke. SpaceX paid a category-leading price for it because it already had distribution to expert software engineers and a firehose of design decisions. Reported ARR figures in 2026 coverage conflict — earlier $1 billion-plus, later annualized numbers in the $2.6–$4 billion range — but the direction is not in dispute. Cursor gives SpaceX the application layer it lacked.
On my board, Cursor is the lead seat. It assigns work. It stays the only git writer. Local first: rehearse the swarm on the laptop before you burn Grok Bot or cloud VM tokens. Last week that looked like Cursor as tender and eight specialist agents sharing one machine’s PowerShell. What broke first was not RAM. It was one shared shell. The fix was a tender plus off-shell work so specialists did not stand in line on the same mutex. Local Cursor is the cheap rehearsal room. The cloud is the tour — after the pattern survives alpha.
Grok Bot is not a chat model
Grok Bot is a persistent-agent product. Own cloud computer. Browser, filesystem, terminal. Signs into the tools you already use, including the ugly ones with no clean API. Multiple bots can run in parallel and message each other. Desktop, iOS, later iPad. Enterprise controls landed on 3 September. Usage is a separate grant from Grok and Cursor token pools.
Access rides on other subscriptions. At launch the gate was SuperGrok Heavy, Cursor Ultra, and Cursor Teams Premium. Within two weeks the floor fell — first to Plus / Pro+ tiers, then, on 26 August, to SuperGrok and Cursor Pro. Prices in current secondary writeups cluster around Cursor Ultra ~$200/month, SuperGrok Heavy ~$300/month, Cursor Teams Premium ~$120/seat. Bundling has already changed once. An older “Heavy includes Ultra” offer was reported as a limited trial, then as a usage grant. My X line that “Ultra isn’t needed and Heavy is the end result” is a user conclusion, not a stable official bundle. Do not buy a plan on a slogan. Read the billing page the week you pay. We keep a vendor-neutral tracker at the AI Stack desk for exactly this reason.
In the Command Center I run, Chief of Staff is not a second operating system. It digests. It files. It waits on Human Gate. Hard bans: never send, post, or pay without a person. Draft-to-self. The Bot that finishes work is useful only if the human still owns irreversible action.
The marketplace is a shelf, not a market
On 4 September the official template marketplace opened at x.ai/bot/marketplace. At first look: 69 public bots, 43 creators, categories across Engineering, Sales, Product, Ops, Finance, Design, Marketing, Recruiting, Customer Success, Personal, Team. A template copies configuration — identity, instructions, skills, routines, selected plugins. It does not copy the original computer, logins, conversation history, API keys, or custom MCP servers.
The first featured first-party template is Haggle Bot, an internal procurement specialist credited to Daniel Gartshein. SpaceXAI’s public case: more than $100,000 identified in a week; 43 unused SaaS seats (~$14,220); about $85,662 in unused SKUs on another product; a weekly tech/office order cut 58 percent ($14,629 to $6,143). Access to Slack, Notion, Drive, Gmail, Hex, Ramp. Human approval required before spend, terms, or vendor contact. Elon amplified the template the same day. The interesting part is not the dollar figure. It is the product shape: a named job, mapped tools, a stop-line written in public, and a one-tap install.
Official marketplace language is share and install, not pay. Multiple independent writeups in the first 48 hours called it a marketplace before a market. No official creator payments as of this writing. That is the missing rail.
The invitation, stated cleanly
If you strip the myth out of my post, the usable claim is this:
SpaceXAI assembled a ladder — Cursor, then Grok Bot, then shared templates, then enterprise agents that can invite people who do not even have a seat. That ladder can be used as more than a product funnel. Each person can become a node. Publish methods other people can run. Treat judgment, taste, and problem selection as the scarce work while execution gets cheaper.
Growing humanity one plugged-in node at a time only works if the tools are a shared workbench, not just a subscription.
This is not official SpaceX policy. It is a participation window. The company is distributing surface area because distribution is how models get used and paid for. Builders can use that surface area as a commons. Those two facts can be true at the same time. We are attaching to this stack as a best guess on how to succeed — and the honest version of “send love” is to use the tools hard, publish what breaks, and feed the useful methods back so the next build is better for everyone on it.
The historic piece is not “they are recruiting us for a 36-month leap.” The historic piece is that the cost of contribution just dropped. A person who can specify a job and judge the output can now ship a reusable teammate. A person who can steer code can now run a desk that used to need a small staff. A person who can only talk can, as of this week on my own sites, publish, clear junk, flag updates, and hand off what they cannot finish — if they leave a receipt.
The loop I keep repeating is not branded. It does not require this stack. A Google Sheet works. Notion works. Whatever you already use. Same mode we run across the operator stack.
Attempt the task yourself. Your main system does as much as it can.
When you hit a roadblock, do not spin noise building scaffolding. Document what you did and open a new task for whoever can finish it — another bot, a different system, or a human.
Close your task with a link to the handoff. That is your receipt.
Two statuses only: your task is done when it is handed off cleanly. The job is done when the receipt lands.
Sometimes the best next actor is a human. That is not a failure. That is the system working. Get in the work, not just the ship.
Giving is not enough. Pay has to follow artifacts.
Until rail three exists, “common cause” is a feeling wearing a storefront. People will still publish. Some already do. Third parties are already charging for templates and agent teams on unofficial shelves. That is not SpaceXAI. Do not conflate the official marketplace with cut-taker shops or anything branded around an unrelated chain. The only official cash program that clearly exists in this neighborhood is security bounty work, which is not bot-building.
If SpaceXAI — or a third party that respects the terms — ever builds the third rail, the design should be boring and strict:
Pay for artifacts, not belonging. A template, an eval, a measured workflow, a verified savings report. Not a membership in the cause.
Require proof the bot ran. Install counts without run logs are theater.
Pay on install, accepted bounty, or measured outcome — and publish the rule so creators are not guessing.
Keep human approval in the loop for irreversible actions. Haggle Bot’s stop-line is the right instinct. Never spend, sign, or send without a person. Copy that into every serious template.
Compensation for connecting people and tools, building bots and workflows, and working with bots alongside the runtime — that is a coherent next design. It is not a current SpaceX program. Treat SpaceXAI as the runtime, not the church.
The risks that ride along
Platform capture. Your methods live on someone else’s computer. Training on user work without sharing upside is the default posture of this industry until a contract says otherwise.
Unsafe third-party bots. A template that looks helpful and holds a login is a new class of supply-chain risk. Official terms reported around late August put the burden on creators to strip secrets and deny endorsement. Read them. Then assume a stranger’s bot will try something you did not expect.
Model choice shrinking. OpenAI’s wind-down notice after the change of control is a reminder that the workbench you love can lose a model family because two companies cannot share a contract. Anthropic’s posture will be watched for the same reason. Plan as if the router gets thinner.
Subscription churn. Bundles already moved twice in August. Heavy is not Ultra. Bot usage is not Grok usage. If you build a livelihood on a bundle, you are building on weather.
Rhetoric. “Common cause” is a beautiful phrase. It is also how a storefront borrows moral language it has not funded. Push back on both “they are upskilling humanity on purpose” and “this is only a subscription trap.” The evidence supports a product-and-distribution play that can be used as a commons if builders — and, eventually, the company — install the missing pay rail.
What to do this week
If you write code: stay in Cursor. Publish the method, not just the repo. Rehearse locally. Promote to Grok Bot only after the pattern survives.
If you cannot live in an IDE: open Grok Bot anyway. Give it one named job with a stop-line. Make it leave receipts on a board a human can see.
If you already have a working bot: strip the secrets, write the anti-jobs in public language, and put a template on the official shelf for reach. Keep source and proof of work somewhere you control. Sell only where the terms allow.
If you run a company: the Enterprise invite-without-a-seat is the quietest on-ramp in the stack. Use it to plug in the people who have judgment and no seat. Do not confuse access with apprenticeship. Assign Human Gate the way you assign budget authority.
If you want to get paid: do not wait for a commons that has not been built. Ship artifacts with receipts. Price the work as work. The historic opportunity is real only for people who publish reusable methods.
Close
I still mean “get in the ship.” I mean it as an operator, not as a spokesman. The next 36 months will move whether or not anyone writes a pretty theory about them. Easier tools will pull more people onto the floor. Some of those people will become nodes. Some of the work will be taken from nodes that used to be paid.
SpaceX bought the leading AI coding workbench and launched an agent layer and a template shelf. That is a real on-ramp for more people to do useful work with machines. The official project is to make Grok useful and commercially central. A human contribution economy only begins when shared bots are not just installable but payable.
The on-ramp is real. The commons is unfinished. Get in the work.
Start here — official doors, no affiliate
Use the tools. Publish what breaks. Feed the useful methods back. That is the honest version of sending love to the companies we are building on.
Will Tygart — Tygart Media. Written 5 September 2026 from the Command Center: Cursor as lead seat, Grok Bot as Chief of Staff, Notion as board, Slack as doorbell, Human Gate on send / post / pay. This essay does not speak for SpaceX, SpaceXAI, Cursor, xAI, X, or Tesla. We want those companies to succeed because we are building on the tools they ship.
Direct Answer (August 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.
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
Account, billing, and a place to store the secret — before you click Create.
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.
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.
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.
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
Copy once. Close the dialog. If you lose it, rotate — do not paste it into chat.
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)
Vault / env / secrets manager. Never chat, git, or a screenshot thread.
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):
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, including the June 2026 lineup with Fable 5).
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.
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.
What models can a new key use? The current lineup as of June 2026 – including Claude Fable 5, Opus 4.8, Sonnet 4.6, and Haiku 4.5; see everything that changed in June 2026.
Get alerted when Claude pricing or limits change
We track Anthropic’s models, pricing, and limits daily and send a short note when something changes that affects what you pay or build. Occasional, no spam.
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)
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)
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
claude-opus-4-8
1M
128K
$5.00
$25.00
Claude Sonnet 4.6
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
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.
The Pivot in One Sentence
xAI has merged into SpaceX and leased its Colossus 1 supercluster—220,000 NVIDIA GPUs, 300 megawatts of compute—entirely to Anthropic, while simultaneously targeting 2 gigawatts of total capacity at Memphis. Elon Musk is no longer primarily trying to win the AI model race. He’s becoming the AI industry’s infrastructure landlord.
Earlier in this series, we asked whether Grok and xAI were building the everything app through X—the social-financial superapp thesis. The answer we arrived at was: maybe, but with real limitations on the model quality and consumer trust needed to pull it off.
Then something happened that reframed the entire question. In early May 2026, xAI merged into SpaceX. Days later, Anthropic—one of xAI’s most direct AI competitors—announced it was renting the entire compute capacity of Colossus 1. All 220,000 GPUs. All 300 megawatts. For Claude. For a reported $3 to $6 billion per year.
Musk’s comment when asked about leasing infrastructure to a competitor: “No one set off my evil detector.”
That’s the tell. When you’re building the everything app, you don’t rent your most powerful asset to your rivals. You use it. The fact that Musk is doing exactly that reveals a strategic logic that the Grok-as-everything-app frame completely misses.
The pivot isn’t from everything app to compute landlord. It’s the recognition that owning the power grid is more valuable than owning any single app that runs on it.
What Colossus Actually Is
What Colossus actually is.
Colossus is not a single data center. It’s a multi-building supercomputing complex in Memphis, Tennessee—and it is currently the largest single-site AI training installation in the world.
Colossus 1, the original facility, holds H100, H200, and GB200 accelerators across more than 220,000 GPU units. That is the cluster Anthropic is now renting entirely.
Colossus 2, the expansion xAI is keeping for its own Grok development, has already expanded to 555,000 NVIDIA GPUs with approximately $18 billion in hardware investment and 2 gigawatts of target power capacity—reached in January 2026 with the purchase of a third Memphis building. Musk’s stated goal: one million GPUs at the Memphis complex, with more AI compute than every other company combined within five years.
As a point of reference: most frontier AI labs operate training clusters in the tens of thousands of GPUs. Microsoft’s Azure AI infrastructure, the largest hyperscaler allocation for AI, operates in the hundreds of thousands across distributed global regions. Colossus at 555,000+ GPUs in a single complex is a different category of infrastructure entirely.
And Musk has publicly noted that xAI is only using about 11% of its available compute for Grok. The rest is—in his framing—available. Available to sell. Available to rent. Available to become the compute backbone of the AI industry whether xAI wins the model race or not.
The xAI-SpaceX Merger: What It Actually Means
The May 2026 merger of xAI into SpaceX as an independent entity is more than an org chart change. It’s a signals-to-strategy reveal.
SpaceX has three things xAI needs at scale: capital (SpaceX generates billions in launch revenue annually), real estate and construction expertise (SpaceX builds rockets and factories at speed), and most critically—rockets. Starship can put mass into orbit economically in a way no other launch vehicle can. SpaceX is already moving toward a Starlink constellation of thousands of satellites. The infrastructure to extend that into orbital data centers is not theoretical.
Anthropic’s announcement noted not just the Colossus 1 ground lease—it also expressed interest in working with SpaceX to develop multiple gigawatts of compute capacity in space. Orbital data centers. Satellite-delivered AI compute. The kind of infrastructure that has zero latency for any application that needs compute without a physical data center address.
Musk has discussed launching a million data-center satellites as a longer-term infrastructure play. That number sounds unreasonable until you consider that SpaceX already operates over 7,000 Starlink satellites and is building Starship specifically for high-volume orbital delivery. The orbital compute thesis isn’t science fiction for SpaceX. It’s a product roadmap.
What the xAI-SpaceX merger does is remove the pretense that these are separate businesses. They’re one integrated infrastructure play: ground-based GPU superclusters plus orbital compute capacity, connected by the world’s only commercially viable heavy-lift reusable rocket.
The Anthropic Deal: A Strategic Reading
The Anthropic deal — a strategic reading.
Let’s be specific about what this deal represents for both sides.
For Anthropic, the deal addresses an acute bottleneck. Anthropic’s annualized revenue grew from roughly $9 billion at end of 2025 to approximately $30 billion by early April 2026—a trajectory that implies an 80-fold increase in usage in Q1 alone. Claude Pro and Claude Max subscriber growth is outpacing Anthropic’s ability to provision compute fast enough. Renting Colossus 1 immediately unlocks 300 megawatts of capacity that would take 18-24 months to build from scratch. For Anthropic, this is a compute emergency solution with strategic upside.
For xAI, the deal is more nuanced. Colossus 1 was already built and operational. xAI is keeping Colossus 2 for Grok development. Renting Colossus 1 generates—depending on which analyst estimate you use—between $3 billion and $6 billion annually in revenue while the asset runs at capacity rather than sitting idle. That revenue funds Colossus 2 expansion, Colossus 3, and whatever comes next. The compute landlord model is self-funding.
The strategic implication: xAI doesn’t need Grok to win the model race for this business model to work. If Claude dominates, Anthropic needs more compute and pays xAI for it. If GPT dominates, OpenAI and its partners need more compute. If Gemini dominates, Google builds its own, but every smaller lab comes to whoever has available capacity. xAI wins in every scenario except the one where everyone else simultaneously builds their own supercomputing megacomplexes—which requires the capital and construction expertise that most AI labs don’t have.
The Grok Situation: Honest Assessment
The Grok situation — honest assessment.
The Anthropic deal does raise real questions about Grok’s trajectory. Grok app downloads have reportedly declined significantly in 2026 as ChatGPT and Claude have gained consumer mindshare. In April 2026, Elon Musk testified in the ongoing OpenAI litigation that xAI trained Grok on OpenAI model outputs—a revelation that raised questions about Grok’s training methodology and original capability claims.
If xAI is using only 11% of its compute for Grok and is renting the rest to a competitor, the implicit message is that xAI is not currently running a max-effort campaign to win the frontier model race. It’s building infrastructure and waiting—or pivoting to a business model where the model race outcome matters less.
This is not necessarily a failure. It may be a more durable strategy. The history of technology infrastructure is full of examples where the company that built the picks and shovels during a gold rush outlasted the miners. AWS didn’t win by building the best e-commerce site. It built the infrastructure that every e-commerce site ran on. The question is whether xAI’s compute infrastructure can fill that role for AI—and the Anthropic deal is the first real evidence that the answer might be yes.
The “Everything App Ability” Thesis
Here’s the reframe that this pivot suggests: maybe the right question isn’t which company will build the everything app. Maybe the right question is which company will own the infrastructure that makes the everything app possible for everyone else.
Every company in this series—Microsoft, Google, Notion, OpenAI, Perplexity, Mistral, Zapier—needs compute. Massive, reliable, cost-effective GPU compute. The frontier model companies are burning through capital building their own clusters because the alternative is depending on hyperscalers (AWS, Azure, GCP) that charge premium rates and may eventually compete directly.
xAI with Colossus is offering a third option: AI-native compute infrastructure, built by a company that doesn’t directly compete on most application layers, at a scale that’s difficult to replicate, at a location (Memphis) with power grid access that many coastal data center markets can’t match.
If you’re building the everything app and you need the compute to run it—Colossus may become the place you go when AWS is too slow, Google is a competitor, and building from scratch takes two years you don’t have.
That’s not the everything app. That’s the everything app’s power grid. And historically, the entity that owns the power grid captures durable, compounding value regardless of which specific applications win the consumer layer.
Space: The Long Game
The orbital compute angle deserves more than a footnote because it’s where this thesis could either collapse into fantasy or become genuinely transformative.
The practical case for orbital data centers is latency equalization: compute in low Earth orbit can serve any point on the Earth’s surface within milliseconds, without the geographic concentration that makes terrestrial data centers vulnerable to regional power outages, natural disasters, or regulatory shutdown. For AI applications that need global deployment at consistent latency—real-time translation, autonomous vehicle coordination, financial systems—orbital compute offers something no ground-based data center geography can.
SpaceX’s Starship dramatically changes the economics of getting mass to orbit. Current launch costs for payloads are measured in thousands of dollars per kilogram. Starship’s target is hundreds of dollars per kilogram—an order-of-magnitude reduction that makes orbital infrastructure financially viable in a way it never was before. The satellite internet analogy is instructive: Starlink was also considered impractical until SpaceX dramatically reduced launch costs, then deployed at a scale that changed the calculus entirely.
Anthropic’s stated interest in orbital compute capacity with SpaceX isn’t a polite corporate gesture. It’s Anthropic hedging its long-term compute dependency on a technology only SpaceX can currently deliver. If even a fraction of that orbital compute vision materializes, xAI/SpaceX’s infrastructure moat becomes essentially unreplicable by any company that doesn’t own a heavy-lift reusable rocket program.
What This Means for the Everything App Race
The xAI infrastructure pivot doesn’t remove Grok and X from the everything app conversation entirely. X still has the distribution, the data firehose, the financial services ambitions, and the brand. Those don’t disappear because Colossus 1 is now running Claude.
But it does add a second thesis that may ultimately matter more: xAI as the infrastructure layer beneath the entire AI economy. Not the everything app—the everything app’s foundation.
In the history of platform technology, the company that owns the infrastructure layer almost always captures more durable value than the company that owns any individual application. TCP/IP outlasted every early internet application. AWS became more valuable than most of the businesses it hosts. The cloud didn’t belong to any one software company—it belonged to the infrastructure providers who made software deployment cheap and fast.
If the AI era follows the same pattern, the question isn’t who builds the best everything app. It’s who builds the infrastructure that makes every everything app possible. And as of May 2026, the most credible answer to that question involves 555,000 GPUs in Memphis, a rocket program that can reach orbit, and a business model that profits whether Grok wins or loses.
Key Takeaway
Elon Musk pivoted xAI from model competitor to infrastructure landlord. By merging into SpaceX, leasing Colossus 1 to Anthropic, and targeting 2 gigawatts of Memphis compute capacity plus orbital data centers, xAI is positioning to capture value from the AI economy regardless of which application layer wins—the power grid, not the appliance.
Related Reading
This article grew out of our everything app series. If you’re tracking where AI consolidation is heading, the full series maps the competitive landscape from nine angles:
Frequently Asked Questions About xAI, Colossus, and the Compute Landlord Pivot
Why did xAI merge into SpaceX?
xAI merged into SpaceX in May 2026 as an independent entity within the broader Musk enterprise. The merger combines xAI’s AI development capabilities with SpaceX’s capital generation, construction expertise, and—critically—rocket launch capabilities. This integration enables the orbital compute strategy: deploying data center satellites via Starship at dramatically lower cost than any competitor could achieve.
What is the Anthropic-Colossus deal?
In May 2026, Anthropic agreed to rent the entire compute capacity of Colossus 1—xAI’s first Memphis supercluster, comprising 220,000+ NVIDIA GPUs and 300 megawatts of power. The deal directly addresses Anthropic’s acute compute shortage during a period of explosive Claude usage growth. Anthropic’s annualized revenue grew from roughly $9 billion at end of 2025 to approximately $30 billion by April 2026. Analysts estimate the deal generates between $3 billion and $6 billion annually for xAI/SpaceX.
How large is the Colossus supercomputer complex?
As of early 2026, the Colossus complex in Memphis spans three buildings and targets 2 gigawatts of total compute capacity. Colossus 2 (kept by xAI for Grok development) has reached 555,000 NVIDIA GPUs with approximately $18 billion in hardware investment. Long-term targets include one million GPUs at the Memphis site. It is currently the largest single-site AI training installation in the world.
What are orbital data centers and why does xAI/SpaceX care about them?
Orbital data centers are computing facilities deployed in low Earth orbit, delivered by rocket. They offer latency equalization (serving any point on Earth within milliseconds), elimination of geographic concentration risk, and compute capacity outside any single regulatory jurisdiction. SpaceX’s Starship reduces launch costs by an order of magnitude compared to existing vehicles, making orbital compute economically viable for the first time. Anthropic’s participation in the deal included expressed interest in developing multiple gigawatts of orbital compute capacity with SpaceX.
Does the compute landlord strategy mean xAI is giving up on Grok?
Not necessarily, but the signals are mixed. xAI is reportedly using approximately 11% of its available compute for Grok development—the rest is available to lease. Grok app downloads have declined in 2026, and April 2026 litigation revealed Grok was trained on OpenAI model outputs. The Colossus 1 lease to Anthropic is the clearest evidence that xAI is not running a maximum-effort campaign on frontier model development and is instead diversifying into infrastructure revenue.
How does the xAI infrastructure play relate to the everything app thesis?
The xAI pivot suggests a reframe of the everything app question. Rather than competing to be the app users interact with daily, xAI/SpaceX is positioning to own the compute infrastructure that powers any everything app—what we’re calling the “everything app’s power grid.” Historically, infrastructure layer companies (AWS, TCP/IP, electricity grids) capture more durable value than any individual application running on top of them. The Anthropic deal is the first concrete evidence that this model may work at AI scale.
May 2026 has been one of Anthropic’s busiest months yet. Here’s everything that shipped, changed, or was announced — plus the confirmed upcoming dates you need to know.
June 2026 Update
Since this page was published, Anthropic has released Claude Opus 4.8 — the new current flagship model, succeeding Opus 4.8. Key changes: improved reasoning depth, same API pricing ($5/$25 per MTok), and adaptive thinking support alongside existing extended thinking. See the current model version tracker for the full model lineup.
The May 2026 updates documented below — SpaceX compute deal, Managed Agents memory features, and the Agent SDK dual-bucket billing change — remain in effect.
Claude Opus 4.8 — Generally Available (April 16, 2026)
Opus 4.8 generally available — capability step.
Opus 4.8 launched April 16 as the current flagship model, priced identically to Opus 4.6 at $5/$25 per million tokens (input/output). Key changes:
Vision resolution: 3× higher at 2,576px (~3.75 megapixels), raising XBOW visual acuity benchmark performance from 54.5% to 98.5%
Coding: 70% on CursorBench (vs 58% for 4.6), resolves 3× more production tasks on Rakuten-SWE-Bench, +13% lift on Anthropic’s internal coding benchmark
Legal reasoning: 90.9% on BigLaw Bench
New effort level:xhigh sits between high and max — five levels total: low / medium / high / xhigh / max
Task budgets: Now in public beta — token spend guidance for longer agentic runs
Tokenizer update: New tokenizer increases token usage roughly 1.0–1.35× for the same content; API pricing unchanged
Breaking change: Opus 4.8 has API breaking changes versus 4.6 — review Anthropic’s migration guide before upgrading
Alongside Opus 4.8, Anthropic launched Claude Design — an Anthropic Labs product for collaborating with Claude to produce visual outputs including designs, prototypes, slides, and one-pagers.
Anthropic announced a partnership with SpaceX to access Colossus 1 compute capacity. The immediate practical impact for subscribers:
Claude Code’s five-hour rate limits doubled for Pro, Max, Team, and seat-based Enterprise plans
Peak-hour limit reductions removed for Pro and Max (previously limits burned faster 5am–11am Pacific on weekdays)
Opus API limits raised for heavy API users
Anthropic is also reportedly evaluating an IPO as early as October 2026, and has disclosed run-rate revenue of $30B (up from $9B at end of 2025). The SpaceX deal comes as the company prepares that filing.
Claude Managed Agents — the fully managed agent harness launched in public beta earlier this year — gained three significant additions:
Dreaming (research preview): A scheduled process that reviews past agent sessions, extracts patterns, and curates memories so agents self-improve over time. Dreaming can update memory automatically or queue changes for human review before they land.
Multiagent Orchestration: A lead agent can now break a job into pieces and delegate each to a specialist sub-agent with its own model, prompt, and tools. Specialists work in parallel on a shared filesystem. Netflix is already using multiagent orchestration for its platform team.
Memory (public beta): Now generally available under the managed-agents-2026-04-01 beta header.
Claude Cowork — Generally Available
Claude Cowork is now GA on macOS and Windows through the Claude Desktop app. New additions with GA: Claude Cowork in the Analytics API, usage analytics, and expanded desktop automation capabilities.
Claude Code — What Shipped in May
Claude Code — what shipped.
Claude Code has been shipping near-daily updates. Notable May additions include:
Plugin URL loading:--plugin-url <url> flag fetches a plugin .zip from a URL for the current session
Project purge:claude project purge [path] deletes all Claude Code state for a project (transcripts, tasks, file history, config) with dry-run support
Package manager auto-update:CLAUDE_CODE_PACKAGE_MANAGER_AUTO_UPDATE runs upgrade in the background on Homebrew or WinGet installs
Push notifications: Claude can now send mobile push notifications when Remote Control is enabled
VS Code Remote Control:/remote-control bridges sessions to claude.ai/code to continue from a browser or phone
1M token context in Claude Code: Available to Max, Team Premium, and Enterprise Opus 4.6/4.7 users at no additional cost — no long-context surcharge as of March 2026
Redesigned desktop app: New session sidebar, drag-and-drop workspace, integrated terminal and file editor, faster diffs, SSH support on Mac
New Connectors Expansion
Claude’s connector directory has grown beyond work tools. New consumer app connectors include AllTrails, Instacart, Audible, Tripadvisor, Uber, and Spotify. The directory now exceeds 200 connectors. Claude surfaces relevant connectors in context during conversations rather than requiring users to browse a directory.
Finance Agent Templates
Anthropic released ten ready-to-run agent templates for financial services work: pitchbook building, KYC file screening, and month-end close workflows. Microsoft 365 add-ins for Excel, PowerPoint, Word, and Outlook are coming soon. A Moody’s MCP app brings Claude into financial data workflows.
Confirmed Upcoming Dates
These are officially announced by Anthropic — not speculation:
June 15, 2026: Claude Sonnet 4 (claude-sonnet-4-20250514) and Claude Opus 4 (claude-opus-4-20250514) are deprecated and retired from the Claude API. Migrate to Sonnet 4.6 and Opus 4.8 respectively before this date.
Microsoft 365 add-ins: Excel, PowerPoint, Word, and Outlook integrations announced as “coming soon” — no specific date published.
Anthropic IPO: Reportedly targeting as early as October 2026 — unconfirmed, no official date.
Google/Broadcom TPU partnership: Multi-gigawatt infrastructure with capacity launching in 2027.
Model Deprecation Summary
Claude Haiku 3 (claude-3-haiku-20240307) has already been retired — all requests now return an error. Migrate to Claude Haiku 4.5. Claude Sonnet 4 and Opus 4 retire June 15, 2026.
What to Watch For
Claude 5 is widely anticipated for Q2–Q3 2026 based on Anthropic’s release cadence, though Anthropic has made no official announcement. The advisor tool — which pairs a faster executor model with a higher-intelligence advisor model for long-horizon agentic workloads — launched in public beta and signals the architectural direction Anthropic is moving toward for complex, multi-step tasks.
The pace of Claude Code releases in particular has accelerated to near-daily — following Anthropic’s own disclosure that engineers internally use Claude for a growing share of their own development work.
Direct Answer (August 2026): Claude Team plan provides pooled, higher message limits per user (approx. 5x Pro capacity shared across the team) with a 5-seat minimum ($20–$100/seat/mo). Team accounts include administrative controls, billing consolidation, and team-wide project workspaces.
The Claude Team plan’s usage limits changed significantly in May 2026. If you’re a Team subscriber and you haven’t noticed yet, you’re now getting substantially more capacity than you were in April — and the free tier got left behind entirely. Here’s exactly what changed, what you have now, and what it means in practice.
Updated May 9, 2026
Rate limits doubled for Team plan subscribers following Anthropic’s SpaceX Colossus 1 compute deal (announced May 6, 2026). Free plan excluded from all increases. This page reflects current limits.
What Changed in May 2026: The SpaceX Rate Limit Increase
On May 6, 2026, Anthropic announced a compute partnership with SpaceX, giving it access to SpaceX’s Colossus 1 data center. The practical result for paying subscribers came fast: rate limits doubled. Here’s the breakdown by tier:
Claude Code Pro and Max: 5-hour rate limits doubled
Team plan (all seats): 5-hour rate limits doubled
Seat-based Enterprise: 5-hour rate limits doubled
Tier 1 API customers: Max input tokens per minute increased 1,500%; max output tokens per minute increased 900%
Peak-hours throttling: Eliminated entirely for Pro and Max subscribers
Free plan: No change. Explicitly excluded from all increases.
The 1,500% input token figure for Tier 1 API is the one that didn’t get much press coverage. That’s a 15× ceiling increase for API users who’ve been running agent pipelines and hitting hard walls. If you’ve been rate-limited during multi-step Claude Code runs, this is the change that matters most.
Team Plan Seat Structure (Still Current)
Team plan seat structure.
The seat types haven’t changed — just the capacity within them. The Team plan still offers two seat types that can be mixed within the same organization:
Seat Type
Annual Price
Monthly Price
Usage vs Pro
Claude Code
Standard
$20/seat/month
$25/seat/month
1.25× more per session
No
Premium
$100/seat/month
$125/seat/month
6.25× more per session
Yes
Both seat types benefit from the May 2026 doubling of the 5-hour rate limit window. A Premium seat’s 6.25× multiplier now applies to a higher baseline than it did before May 6.
How the 5-Hour Rate Limit Window Works
How the rate-limit window works on Team.
Anthropic uses a rolling 5-hour window for usage limits, not a daily reset. Here’s what that means practically:
Usage is measured across a rolling 5-hour window, not midnight-to-midnight
If you hit the limit, you wait for the oldest usage to roll off — not for a fixed reset time
Heavy burst usage depletes your window faster than spread-out usage
The May 2026 doubling means the ceiling within that window is now twice as high
Peak-hours throttling — the extra restriction that kicked in during high-demand periods — is now eliminated for Pro and Max. Team plan benefits from the doubled limit floor; the throttling elimination is Pro and Max specific.
Deprecation notice: Claude Sonnet 4 and Opus 4 (original 4.0-generation, 20250514 date-string model IDs) were retired June 15, 2026. Update any API integrations before that date.
What the Free Plan Doesn’t Get
The May 2026 rate limit increase does not apply to free accounts. Anthropic explicitly excluded the free tier from all capacity increases tied to the SpaceX deal. Paid plans now have a substantially higher ceiling while the free ceiling stays the same. If you’re hitting limits regularly on the free tier, the May 2026 changes are pressure toward upgrading — not relief.
Team Plan vs Pro: Which Limit Structure Fits You?
Team vs Pro — which limit structure fits.
Individual power user: Pro ($20/month) with throttling eliminated is a strong option.
Team with Claude Code needs: Team Premium seats ($100/seat/month annually) give Claude Code access, 6.25× multiplier, and the doubled 5-hour window.
Team without Claude Code needs: Standard Team seats ($20/seat/month annually) for shared access at higher limits than individual Pro.
Frequently Asked Questions
Did the Team plan rate limits actually double in May 2026?
Yes. Anthropic confirmed the 5-hour rate limit doubled for Team plan subscribers following the SpaceX Colossus 1 compute deal announced May 6, 2026. This applies to both Standard and Premium seats.
Does peak-hours throttling elimination apply to Team plan?
The peak-hours throttling elimination was announced specifically for Pro and Max subscribers. Team plan benefits from the doubled rate limit floor; throttling elimination was not announced for Team.
What happens when I hit a Team plan usage limit?
Claude notifies you that you’ve reached your usage limit. With the 5-hour rolling window, you can continue once older usage rolls off — you’re not waiting for a midnight reset. Burst usage depletes the window faster than spread usage over the same period.
Are Claude Sonnet 4 and Opus 4 still available on Team?
They remained available until June 15, 2026, when they were retired. Since then, the active lineup has been Fable 5, Opus 4.8, Sonnet 5, and Haiku 4.5.
Does the 1,500% Tier 1 API increase apply to Team plan API usage?
The 1,500% input and 900% output token increases apply to Tier 1 API customers specifically. Team plan through claude.ai uses the doubled 5-hour window. Both benefits apply in their respective contexts if you’re a Tier 1 API customer and a Team subscriber.
Is the free plan getting any rate limit improvements?
No. The free plan was explicitly excluded from all rate limit increases in the May 2026 SpaceX announcement.
💼 Deploying Claude or AI Infrastructure in Your Business?
