Two of the largest models ever released shipped inside five days of each other, and one of them costs a quarter of what the leader charges. OpenAI cut the price of a three-week-old model by 80 percent. The Model Context Protocol shipped its biggest revision since launch and deprecated three primitives on a twelve-month clock. Underneath all of it, the physical buildout kept accelerating while four American states moved to slow it down.
Here is what happened between July 29 and August 5, 2026, in models, tooling, standards, and infrastructure.
Models: Alibaba Ships 2.4 Trillion Parameters and a Price Tag
Alibaba released Qwen3.8-Max on August 3, the largest model the Qwen team has ever shipped. It carries 2.4 trillion total parameters and activates roughly 95 billion per token through a sparse mixture-of-experts architecture. Context runs to 1 million tokens. The model accepts text, images, and video as input and returns text.
The architecture number matters more than the headline number. A 2.4 trillion parameter dense model is not servable at any reasonable cost. A 2.4 trillion parameter MoE that activates 95 billion per token has the serving profile of a much smaller model with the knowledge capacity of a much larger one. That gap between total and active parameters is the entire economic argument for MoE, and Alibaba is now running it at a scale nobody had shipped before this summer.
Alibaba published Arena placements alongside the launch. Qwen3.8-Max ranks fifth in Text Arena, second in Vision Arena, and fourth in Frontend Code Arena with a score of 1,668, which puts it 37 points behind Claude Opus 5. Those are third-party leaderboard positions rather than vendor benchmarks, which makes them more useful than most launch numbers. Alibaba's broader claim that its performance sits in the global top tier trailing only Anthropic's Claude family is a vendor characterization, so treat it accordingly.
The autonomous coding claim
The launch centers on long-horizon work rather than single-turn quality. Alibaba reports that in internal testing, Qwen3.8-Max spent about 16 days building and maintaining the oh-my-cli project, producing 265 commits, 127 pull requests, and 151 issues without human intervention. That figure comes from Alibaba's own testing and has not been independently reproduced.
Take the number with salt and the direction seriously. The interesting metric in agentic coding stopped being SWE-bench pass rate a while ago. It became how long a model stays coherent before it needs a human to reset the context. A 16-day run, if it holds up, is a different category of claim than a 70 percent score on a benchmark of isolated bug fixes. Every lab is now optimizing for that number, and the ones that publish it are the ones who think they lead.
Pricing and access
Qwen3.8-Max is live through Alibaba Cloud Model Studio and QwenCloud. The API is OpenAI-compatible and DashScope-compatible, so switching an existing integration is a base URL and model ID change rather than a rewrite. Independent analysis puts output tokens at roughly 24 percent of Claude Opus 5's price and input tokens at about 40 percent.
Alibaba committed to releasing open weights within about a week of launch, for both Qwen3.8-Max and a smaller Qwen3.8-27B. As of this writing neither is on Hugging Face and no license has been named. This is the first time Alibaba has promised open weights for a Max-tier model. Qwen3.7-Max stayed API-only, and the open-weight line ran separately through Qwen3.6.
Anyone planning around that open-weight release should do the arithmetic first. A 2.4 trillion parameter checkpoint at 4-bit precision needs roughly 1.2 terabytes for weights alone. A single Nvidia H200 carries 141 GB. Even eight cards leave you short. The open weights matter for research groups, sovereign deployments, and organizations with multi-node clusters. For a startup with a few GPUs, the hosted API is the deployable artifact and the 27B checkpoint is the one to watch.
Alibaba also launched QwenWork, an all-in-one workplace agent platform, in public beta on the same day. Alibaba stock rose 4.5 percent in premarket trading in New York and 7 percent in Hong Kong on the announcement.
DeepSeek re-post-trains rather than rebuilds
Four days earlier, DeepSeek published DeepSeek-V4-Flash-0731 on Hugging Face and moved the official V4-Flash API into public beta. The model card is unusually clear about what changed. The architecture and parameter count stay the same as the April preview: 284 billion total parameters, 13 billion active, 1 million token context, 384,000 token maximum output. Every gain comes from a new post-training pipeline focused on coding, agents, reasoning, and tool use.
That is a notable choice. Most labs answer a competitive week with a bigger model. DeepSeek answered with the same model, trained differently, and shipped it under an MIT license on Hugging Face with no gate.
The checkpoint ships with the DSpark speculative decoding module attached, which is why Hugging Face reports 304 billion parameters for the repository against a 284 billion base. On the API side, deepseek-v4-flash now supports the Responses API format natively and is adapted for Codex-style agent workflows. The V4-Pro API and the app and web models were not updated.
Read the benchmark numbers carefully
DeepSeek reports 82.7 on Terminal-Bench 2.1, 54.2 on NL2Repo, and 70.3 on Toolathlon Verified. Two other published scores use DeepSeek's internal test sets, DSBench-FullStack and DSBench-Hard, which makes them unverifiable by anyone outside the company.
A 25.8-point Terminal-Bench jump circulated widely after launch. DeepSeek's own model card does not report that figure. The card puts 0731 at 82.7 on Terminal-Bench 2.1 and the April preview at 61.8 on the same test, which is a 20.9-point gain. There is one clean independent check on the baseline. Artificial Analysis measured the then-current endpoint at 61.8 on Terminal-Bench 2.1 in a July 27 snapshot, four days before 0731 shipped, matching DeepSeek's preview column to the decimal. Two parties, same checkpoint, same benchmark version, same answer.
The second widely repeated claim is that V4 Flash matches Claude Opus 4.8 at a fraction of the price. DeepSeek published a nine-row comparison against Opus 4.8. Opus 4.8 leads all nine rows. The price argument is real. The parity argument is not what DeepSeek's own table says.
For the code-agent benchmarks, DeepSeek used a not-yet-released minimal mode of DeepSeek Harness with reasoning intensity set to max. Benchmark numbers produced with an unreleased harness are not reproducible by readers, which is worth flagging every time it happens regardless of which lab does it.
The prices
DeepSeek lists deepseek-v4-flash at $0.14 per million input tokens on a cache miss, $0.0028 on a cache hit, and $0.28 per million output tokens, with a 2,500 request concurrency limit. Those rates did not change with 0731. V4 Pro sits at $0.435 input and $0.87 output.
DeepSeek has published a plan for peak pricing that doubles every billing item during two Beijing-time windows, 09:00 to 12:00 and 14:00 to 18:00, for seven hours a day total. No effective date has been announced. Anyone modeling annual spend on DeepSeek should account for that, because a 2x multiplier across the working day is not a rounding error.
Self-hosting is a different calculation. The weights are MIT-licensed and ungated, but every expert stays resident in memory even though only 13 billion activate per token. DeepSeek's own vLLM example serves the model on a single four-way GB300 node. Unsloth's dynamic GGUF builds put the lossless 8-bit version at 162 GB and a 3-bit version at 103 GB, needing roughly 110 GB of combined RAM and VRAM.
The open-weight race has a scoreboard now
Step back from either release and the shape of the year becomes clear. Moonshot AI shipped Kimi K3 in mid-July as a 2.8 trillion parameter open-weight model, the largest open-source model by parameter count. Alibaba previewed Qwen3.8-Max at the World AI Conference in Shanghai on July 19, two days later, and shipped it August 3 with an open-weight commitment attached. DeepSeek put a 284 billion parameter MIT-licensed checkpoint on Hugging Face on July 31 with no gate and no waitlist.
Three labs, three different strategies, one shared conclusion: releasing weights is now a competitive move rather than a concession.
The strategies differ in ways that matter to anyone choosing a model. DeepSeek optimizes for cost per unit of work and ships weights immediately under a permissive license. Moonshot goes for maximum scale in the open. Alibaba runs a hosted flagship first and follows with weights, pairing the frontier checkpoint with a small one that ordinary hardware runs.
That last pairing is the pattern to watch. A 2.4 trillion parameter open checkpoint is a research artifact and a sovereign-deployment artifact. A 27 billion parameter checkpoint from the same training run is a product. Labs that ship both get the prestige of the big number and the adoption of the small one, and the small one is what ends up embedded in a thousand applications.
For teams evaluating this, the practical question is not which model tops a leaderboard. It is which of these you can commit to for eighteen months. An MIT-licensed checkpoint you host yourself has a different risk profile than a hosted API from any vendor, and both differ from a model whose weights are promised but not yet published under a license nobody has read. Qwen3.8-Max sits in that third category right now. Wait for the license before you plan around it.
OpenAI cuts a three-week-old model by 80 percent
The pricing news of the week came from OpenAI. On July 30 the company reduced GPT-5.6 Luna by 80 percent and GPT-5.6 Terra by 20 percent. Luna went from $1 and $6 per million input and output tokens to $0.20 and $1.20. Terra went from $2.50 and $15 to $2 and $12. Sol, the flagship, stayed at $5 and $30.
GPT-5.6 reached general availability on July 9. A price cut of that size 21 days after launch is not a routine adjustment.
OpenAI attributes the reduction to efficiency improvements in the models and the infrastructure serving them. The cut also applies to how Luna and Terra usage is metered inside ChatGPT Work and Codex. Subscription prices and quota budgets stay the same, and the two cheaper tiers now consume fewer credits, which functions as a cap increase without touching the price list. Rollout on AWS followed the same day.
The third item in the announcement runs the opposite direction. Sol gains a Fast mode at $10 input and $60 output per million tokens for up to 2.5 times the standard speed at the same stated output quality. It replaces Priority Processing in the API and aligns with /fast in Codex. Existing API requests tagged priority keep working. Doubling the price for speed is a familiar pattern, and renaming it alongside a set of cuts makes the announcement read cheaper than it is.
Two structural effects fall out of the July 30 numbers. Terra now undercuts the older GPT-5.4 at $2 and $12 against $2.50 and $15, which kills the shorthand that Terra prices like 5.4. And Luna became the cheapest model in the flagship table, roughly four times under gpt-5.4-mini at $0.75 and $4.50. Anyone still reasoning from June's pricing has a stale mental model.
What the price moves are actually responding to
The pressure has a number attached. CNBC reported on July 7 that Chinese models captured 46 percent of United States enterprise token usage on OpenRouter. That statistic explains the shape of OpenAI's cut better than any efficiency story. Sol stayed at full price because nothing in the open-weight world is competing for flagship reasoning work. Luna dropped 80 percent because the classification, extraction, and routing workloads it serves are exactly where a $0.14 open-weight model wins on spreadsheet math alone.
The competitive picture at the top is worth holding in view. Anthropic's Fable 5 lists at $10 and $50 per million tokens. Sonnet 5 sits at an introductory $2 and $10 through August 31, moving to $3 and $15 after that. Anyone sizing an annual budget against this week's price lists will be redoing the math in September.
The larger point for practitioners is that unit price stopped being the comparison axis. What matters now is how much completed work you get per dollar. A model at $0.14 that needs three attempts costs more than a model at $1 that needs one. DeepSeek's own Intelligence Index run generated 210 million tokens against a median of 100 million for the same evaluation, which is the sort of verbosity that quietly doubles a bill. Measure task completion cost on your own workload, not list price.
Tooling: Harnesses Converge on Each Other's Formats
The most telling tooling development this week was not a feature. It was DeepSeek adding native Responses API support and adapting its model for Codex-style agent workflows.
Think about what that means. A Chinese lab shipped compatibility with a competing American lab's agent harness format as a headline feature of a model release. The same release keeps OpenAI-compatible endpoints. Alibaba's Qwen3.8-Max ships OpenAI-compatible and DashScope-compatible APIs. The API surface has effectively standardized around whatever OpenAI shipped, and every other vendor treats matching it as table stakes.
For teams, this is the good outcome. Model switching is now a base URL and a model ID for a large fraction of workloads. The lock-in that mattered in 2024 has moved up the stack, into prompts, evaluation suites, tool definitions, and the agent harness itself.
Claude Code keeps shipping small
Anthropic released Claude Code v2.1.221 on August 3, which adds a Focus view that collapses tool activity into compact summaries. That sounds cosmetic. It is not. Anyone who has watched an agent run for twenty minutes knows the problem: the transcript fills with file reads, greps, and bash calls until the actual reasoning is buried. Collapsing tool noise into summaries makes long autonomous runs reviewable by a human, which is the bottleneck on trusting them.
The July 24 release, v2.1.219, made Claude Opus 5 the default model with expanded context and stronger security controls. The pace here is worth noting on its own. Claude Code has shipped 348 tracked releases. That is a release cadence closer to a web service than a developer tool, and it changes what "stable" means for anything built on top of it.
Antigravity builds out the agent platform layer
Google's Antigravity changelog this period reads like infrastructure work rather than feature work, which is usually the sign of a product going from demo to deployment.
The SDK gained OpenTelemetry tracing support, translating session, turn, step, and tool lifecycle events into standard GenAI-compliant semantic spans, with task-safe active span propagation for tool execution. That is the single most useful thing on the list. An agent that runs for an hour across dozens of tool calls is an observability problem, and until this year most teams were solving it with print statements. Standard spans mean agent traces land in the same dashboards as everything else.
The release also added declarative subagent configurations through SubagentConfig and SubagentCapabilities, letting teams construct static subagents with declarative instructions and tools rather than assembling them in code. Lifecycle hook routing moved to the connection layer, covering session start, pre-turn and post-turn, and session end hooks. A built-in antigravity_guide skill gives in-context reference for the 2.0 release, the CLI, the IDE, and the SDK.
Antigravity 2.0, announced at Google I/O on May 19, split into a unified harness with a redesigned desktop app and a standalone CLI, adding specialized subagents, cross-platform terminal sandboxing, credential masking, and hardened Git policies. It ships a Managed Agents API and an SDK for self-hosted deployments.
Credential handling is now a product feature
Three separate items this week touched agent permissions and credentials, which is the correct amount of attention for the risk involved.
Antigravity ships credential masking and terminal sandboxing. Claude Code's July 24 release added stronger security controls alongside the Opus 5 default. Cursor's Auto-review run mode, shipped May 29, gates Shell, MCP, and Fetch tool calls through an allowlist, a sandbox, and a classifier subagent, which sits between fully manual approval and full autonomy.
The pattern across all three: nobody is shipping a binary autonomy switch anymore. The middle ground, where an agent runs freely inside a defined boundary and stops at the edges, is where every serious tool has landed. If your team is still running agents with blanket approval because per-call prompts were annoying, the tools caught up and the middle option now exists.
Billing keeps moving under everyone
GitHub Copilot moved all plans to usage-based billing with AI Credits on June 1. Pro includes $15 a month in credits, Pro+ includes $70, and Max includes $200. Premium model selections draw from that pool. Legacy request-based annual subscribers keep 300 premium requests a month on Pro and 1,500 on Pro+ at $0.04 each.
One access caveat still stands as of August 2: new self-serve signups for Copilot Business remain paused for organizations on GitHub Free and GitHub Team plans, in effect since April 22. Those organizations need Enterprise Cloud or a sales conversation. Individual Pro, Pro+, and Max signups are open.
Cursor runs a similar included-usage-plus-burn-rate model. Pro at $20 a month includes about $20 of API-rate usage, Pro+ at $60 includes $70, and Ultra at $200 includes $400.
The through-line is that per-seat pricing is dying in this category. Agents consume compute in wildly variable amounts depending on task, and no vendor can price a seat that runs a 16-day autonomous coding job the same as one that autocompletes. Budget accordingly, and instrument your usage before you commit to an annual contract.
Microsoft's in-house coding model, announced at Build 2026 under the Project Polaris name, is slated to become the default inside GitHub Copilot starting this month. Watch for whether that changes Copilot's credit math, because a first-party model has different unit economics than a purchased one.
The harness matters as much as the model
One quiet detail from the DeepSeek release deserves its own paragraph. The published code-agent benchmark numbers came from a not-yet-released minimal mode of DeepSeek Harness with reasoning intensity set to max. The model is the same either way. The harness changed the score.
This is the most underrated variable in agentic coding right now. The same model scores differently depending on how the harness structures the loop, what tools it exposes, how it handles failed commands, how much of the file tree it puts in context, and when it decides to stop. Published numbers from one lab's harness do not transfer to another lab's harness, and neither transfers cleanly to yours.
The practical consequence is that benchmark comparisons across vendors have gotten close to meaningless for tool selection. What has not gotten meaningless is running your own tasks through each harness and measuring the result. Pick five representative pieces of work from your actual backlog. Run each through Claude Code, Codex, Cursor, and Antigravity with whatever model each defaults to. Measure time to a mergeable pull request, how many times a human intervened, and total spend. That takes a week and tells you more than any leaderboard.
The second consequence is that harness portability is worth paying for. A model that supports multiple harness formats natively, the way DeepSeek now supports both its own and the Responses API, lets you change one variable at a time. That is worth more than a couple of points on a benchmark you cannot reproduce.
Standards: MCP Ships Its Largest Revision Since Launch
The 2026-07-28 Model Context Protocol specification landed on schedule on July 28, and it is the biggest change to the protocol since it launched.
Some scale first. The maintainers report close to half a billion downloads a month across the Tier 1 SDKs, with both the TypeScript and Python SDKs crossing one billion total downloads. MCP went from a way to wire up local tools to the connective layer for agentic workflows in about eighteen months.
The protocol is stateless now
The headline change is that MCP is stateless at the protocol layer. Six Specification Enhancement Proposals work together to get there, completing a plan the maintainers laid out in December.
Concretely, protocol-level sessions and the Mcp-Session-Id header are gone. Any server instance behind ordinary HTTP infrastructure answers any request. A remote MCP server that previously needed sticky sessions, a shared session store, and deep packet inspection at the gateway now runs behind a plain round-robin load balancer, routes traffic on an Mcp-Method header, and lets clients cache tools/list responses for as long as the server's ttlMs permits.
That last detail deserves emphasis. Cacheable list results remove a per-connection round trip that every client was paying on every session. At the scale MCP now runs, that is a meaningful reduction in traffic for zero application change.
The revision also brings Multi Round-Trip Requests, header-based routing, authorization hardening aligned more closely with OAuth and OpenID Connect deployments, a formal extensions framework, and a formal deprecation policy.
What breaks and on what clock
The deprecations are the part to plan around, and the maintainers attached real timelines to them.
Roots, Sampling, and Logging are deprecated under SEP-2577. All three keep working for at least twelve months. New implementations should not adopt them. If you built a server that leans on Sampling to ask the client's model for a generation, start planning the migration now rather than in month eleven.
Dynamic Client Registration is formally deprecated in favor of CIMD. DCR continues to work for backward compatibility and will be removed in a future spec version.
The legacy HTTP+SSE transport is officially deprecated with a year-long offramp. Streamable HTTP has been the recommended transport since the 2025-03-26 revision, so most active deployments already moved.
Tasks moved out of the experimental core into the io.modelcontextprotocol/tasks extension, with a poll-based tasks/get and a new tasks/update under SEP-2663. Change notifications moved from the old HTTP GET endpoint to a single subscriptions/listen stream that clients opt into per notification type.
All four Tier 1 SDKs speak 2026-07-28 as of the release date. The Rust SDK supports the new spec in beta.
Adoption started immediately
Vercel MCP now serves both the stateless 2026-07-28 protocol and the 2025 protocol from a single endpoint, with mcp-handler 2.x, as of August 1. Four days from spec publication to a major platform shipping dual-protocol support is fast, and the dual-serving approach is the right pattern for anyone else migrating. Serve both, watch your client mix, and drop the old one when the traffic justifies it.
Why a formal deprecation policy is the real story
The stateless core will get the attention. The deprecation policy matters more over a five-year horizon.
MCP spent its first period as a fast-moving protocol with a small maintainer group, shipping changes as they made sense. That works until enough production systems depend on you. A formal policy that says what gets deprecated, how long it keeps working, and when it disappears is what lets an enterprise commit to a protocol without assuming it will break in eight months. Combined with the extensions framework, which gives new capabilities a home outside the core, the protocol now has a way to grow without dragging every implementation along for every experiment.
The same instinct is visible in Apache Parquet this week, where the community voted on a versioning scheme specifically to define what forward incompatible means and how to release it. Two entirely different communities arrived at the same conclusion in the same week: at a certain scale, the compatibility promise has to be written down.
Infrastructure: Capex Up, Permits Down
The physical buildout had its loudest week in months, and for the first time the regulatory pushback registered at similar volume.
The capex numbers keep climbing
Amazon lifted its 2026 AI infrastructure spending to $220 billion on July 31 and still expects capacity to trail customer demand. Read that second clause again. The largest cloud provider on earth is spending a fifth of a trillion dollars this year and telling investors it will not be enough.
The framing shift in the Q2 earnings calls is the more useful signal. Microsoft, Alphabet, and Meta all moved the conversation away from aggregate capex toward time-to-energy, large-scale networking, power procurement, and how fast infrastructure converts into revenue-generating compute. Capex is no longer the constraint. Getting power to a site and turning it into billable inference is.
That reframing explains most of the project news. Meta is expanding its Hyperion campus in northeast Louisiana into what it describes as a 5 GW AI supercluster, at a scale utility planners say has implications beyond conventional hyperscale. Meta's first Canadian data center in Sturgeon County, Alberta, represents more than $9 billion for a 1 GW campus. Google was identified as the owner of Project Tembo, a 2.7 GW facility in Cheyenne, Wyoming, the largest data center in that state.
OpenAI announced Project Camellia in Effingham County, Georgia. The detail worth noting is the reporting that Georgia Power had documented a 3,200 MW customer commitment months before the public announcement and was reviewing an anonymized 3,210 MW project with a matching timeline. Utility interconnection filings are now a leading indicator of AI infrastructure announcements, and people are reading them.
Core Scientific doubled its leased AI capacity to roughly 1.1 GW through a 15-year infrastructure agreement with AMD. DeepInfra opened its first international facility in Toronto, a 1.7 MW site with more than 1,000 Nvidia Blackwell B300 GPUs.
Four states applied brakes in one month
The counter-movement is now real and it is bipartisan.
New York issued an executive order pausing certain permits for new data centers over 50 MW pending rules on grid costs, water use, and host community benefits. Texas Governor Greg Abbott ordered a statewide audit of data center projects in the ERCOT interconnection queue on August 3. North Carolina lawmakers repealed the sales tax exemption on electricity for data centers while keeping equipment incentives. Nebraska Governor Jim Pillen issued an executive order blocking new data center projects from receiving tax incentives under the ImagiNE Nebraska Act.
A separate Virginia report released July 30 found groundwater running dry for new data centers in parts of the state.
The Texas audit is the one with the sharpest teeth. ERCOT's interconnection queue is where a large share of United States AI capacity is waiting, and queues are notoriously full of speculative projects that will never break ground. An audit that separates real projects from placeholders changes the planning picture for everyone in line, including the serious builders.
For anyone forecasting compute availability into 2027, permitting and power are now the variables to model. Chip supply is a solved problem compared to getting 500 MW approved in a state where voters have started paying attention to their utility bills.
Memory stays the hard constraint
The memory picture has not improved. High-bandwidth memory production remains effectively sold out, with a large majority of high-end DRAM and HBM output going to AI data centers. SK hynix holds the dominant share of HBM4 volume allocated to Nvidia's Vera Rubin platform and formalized a multiyear co-development agreement with Nvidia covering design as well as supply.
The mechanics of why memory binds rather than compute are worth understanding if you are sizing inference deployments. A large MoE model keeps every expert resident even though only a fraction activate per token. DeepSeek-V4-Flash makes this concrete: 284 billion parameters resident, 13 billion active, and you pay for the resident count in memory. Qwen3.8-Max makes it starker at 2.4 trillion resident against 95 billion active. MoE saves you compute and flops. It saves you nothing on memory capacity.
That is why the interesting quantization work matters so much. Unsloth's 3-bit build of V4 Flash at 103 GB is what turns a datacenter artifact into something a well-equipped team runs on their own hardware. Expect a similar effort around Qwen3.8-27B the moment those weights land.
Novel form factors move from concept to engineering
Samsung Heavy Industries signed an engineering agreement with Mousterian Corporation on August 3 to advance factory-built, moored floating data centers designed for AI workloads. Each unit would provide 50 MW of critical IT capacity, with initial deployments planned for Texas and other United States markets. SHI unveiled the concept at Posidonia 2026 in June.
Floating data centers sound like a stunt until you line them up against the permitting news above. A factory-built, moored 50 MW unit sidesteps land acquisition, local zoning fights, and a large part of the cooling water argument. Whether the economics work is an open question. The fact that a major shipbuilder moved from concept to a signed engineering agreement in two months says something about how badly the industry wants alternatives to the conventional siting process.
Elsewhere, Pure Data Centres Group committed €1.5 billion to a 110 MW AI campus in Seinäjoki, Finland, with potential expansion to a €7.5 billion campus exceeding 550 MW. ByteDance reportedly began construction on a $38.4 billion facility at the Pecém port complex in Ceará, Brazil, starting at 200 MW with expansion toward 1 GW. Nebius launched a European AI infrastructure company headquartered in Amsterdam. Mitsubishi Estate plans roughly $9.3 billion for 2.5 GW of Japanese capacity.
The Uptime Institute's 2026 survey, published July 31, found AI driving broad uncertainty across data center operations, which is a polite way of saying operators do not know what their facilities will be asked to run in three years.
Interconnect is the third constraint
Power and memory get the headlines. Networking is the quieter limit, and it showed up directly in the Q2 earnings framing when Microsoft, Alphabet, and Meta all named large-scale networking alongside power procurement.
The reason is structural. Modern training and large-model inference run across thousands of accelerators, and the fabric connecting them determines how much of that hardware does useful work. A cluster with fast chips and a slow fabric spends its time waiting. Proprietary interconnects like NVLink deliver the bandwidth but tie the design to one vendor's roadmap and pricing. Ethernet-based scale-up designs trade some performance for supply chain independence and lower cost, which is why several hyperscalers keep investing in them.
For anyone buying inference capacity rather than building it, this is mostly invisible until it isn't. Fabric design is what determines whether a provider can serve a 2.4 trillion parameter MoE across multiple nodes at reasonable latency. Ask about it when you evaluate a neocloud, because a provider with plenty of GPUs and a thin fabric cannot serve the models people now want to run.
What This Means for the Data Layer
Four things happened this week that connect directly to how teams manage data.
The price of a token collapsed for the second time this year, which changes what is worth doing with data rather than just what it costs. At $0.14 per million input tokens, running a model across an entire table stops being an experiment and becomes a batch job. The bottleneck moves from inference cost to data access: how fast can you get the right rows in front of the model, and how do you govern what the model is allowed to see.
MCP going stateless matters for exactly that reason. An agent that queries your warehouse through an MCP server no longer needs sticky sessions, which means it scales the way any other HTTP client scales. Cacheable tool lists mean an agent discovering what tables and tools exist does not pay a round trip every time. The protocol got out of the way of high-volume agent traffic against data systems.
The context windows are the third piece. Both flagship releases this week ship 1 million token context. A million tokens is a lot of rows, and teams keep discovering that stuffing context is cheaper to build than a retrieval pipeline. It is also slower, more expensive per query, and harder to govern. The right pattern remains narrow, well-governed access to fresh data rather than dumping a table into a prompt, and it stays right even as context grows.
Fourth, autonomous coding runs measured in days rather than minutes change what agents do to your data infrastructure. An agent that operates for 16 days generates schema changes, writes pipelines, and creates tables. Governance that assumed a human reviewed every write does not survive that. Lineage, catalog-level access control, and a full audit trail stop being compliance features and become operational necessities.
The Apache side of this ecosystem is moving in the same direction. Apache Polaris shipped 1.7.0 this week with per-principal attribution in cloud audit logs and feature flags that force the catalog to own every table location. Apache Iceberg voted read restrictions and variant support through its REST spec. Those are catalogs preparing for a world where the thing issuing queries is not a person.
Practitioner Takeaways
Reprice your workloads. Every model you evaluated before July 30 has different economics now. Luna dropped 80 percent, Terra 20 percent, and two frontier-class open-weight options entered the market. If you built a routing layer that sends easy work to cheap models, the thresholds moved.
Measure completion cost, not token price. A cheap model that retries three times is expensive. Build an evaluation set from your real tasks and compare total cost to a correct answer, including retries and verbose reasoning traces.
Start the MCP migration now. Roots, Sampling, and Logging have a twelve-month clock. The legacy HTTP+SSE transport has a year-long offramp. Dynamic Client Registration is deprecated. None of this breaks today. All of it breaks eventually, and twelve months disappears fast.
Turn on agent tracing. OpenTelemetry spans for agent sessions exist now in at least one major SDK. If you are running multi-step agents in production without traces, you are debugging blind.
Check your credit math before renewal. Usage-based billing landed across Copilot and Cursor, and Sonnet 5's introductory pricing ends August 31. Anything you budgeted in the spring needs a recalculation.
Watch power, not chips. If your 2027 capacity planning assumes GPU availability is the constraint, revisit it. Four states moved against data center development in one month, and the largest cloud provider says its own capacity will trail demand.
Looking Ahead
The Qwen3.8-Max and Qwen3.8-27B open weights are due within days. Watch for the license, the activated parameter disclosure, and how fast the quantization community produces a runnable build. The 27B is the one most teams will actually deploy.
Expect responses to the OpenAI price cut. Anthropic's Sonnet 5 introductory pricing ends August 31, which is the next dated pricing event on the calendar. DeepSeek's peak-hour 2x multiplier is announced but undated, and Google has been quiet on pricing for several weeks.
On standards, watch the MCP client migration rate. Vercel moved in four days. The interesting number is how many servers are still 2025-only in October, because that determines whether the twelve-month deprecation windows hold or get extended.
On infrastructure, the Texas ERCOT audit results will tell you more about real 2027 capacity than any capex announcement. And the Community over Code hackathon in Glasgow runs October 11 to 14, with task lists due from projects now.
One larger thing to watch through the rest of the year. Every story in this issue points at the same underlying shift: the industry is done treating capability as the only scarce resource. Price, power, permits, memory, fabric, and protocol stability are the constraints teams actually hit. The labs that win the next stretch are the ones that make a capable model cheap and predictable to run, and the platforms that win are the ones that make it safe to point that model at real data. Capability was the story of the last three years. Delivery is the story of this one.
Keep Going Deeper
If you want more than a weekly roundup, the books go further. I write about AI-assisted development, agent workflows, MCP, Apache Iceberg, lakehouse architecture, and the data infrastructure all of this runs on. Every title I have written lives in one place.
Top comments (0)