The Read

Anthropic told prospective IPO investors it booked $16.8 billion of revenue in a single quarter, up about 45% on the quarter before, profitable on an adjusted basis for the second quarter running, and earning $1.70 of revenue for every dollar it spends on compute. Earlier the same day Gartner published the arithmetic saying the build-out underneath it cannot repay itself: nearly $1 trillion of AI infrastructure spending this year and $6 trillion more through 2030, against a revenue ceiling it puts at $3.6 trillion. By the close CoreWeave had fallen more than 15% and its 2032 bonds were yielding close to 15%. Both halves are true and they are not in tension: the model layer is compounding faster than almost any software business ever has, while the layer that finances the buildings is being repriced by people who sized those balance sheets for a different cost curve. The day-zero read has not changed — the returns are accruing to whoever points cheap intelligence at an old problem, not to whoever owns the building it runs in.

Tide

No shift. One confirmation of cost-collapse, and it arrives from the one side this brief has never had a public number for. We have logged the price of intelligence falling, the volume consumed rising, the frontier's share of demand collapsing, the realised margin on a quarter-gigawatt of inference, and the move into own silicon. All of those are the buyer's view. Anthropic's disclosure is the seller's: prices came down repeatedly across the year and the seller's economics got better anyway. The tide holds, and the case that falling prices are value-destructive for the people selling intelligence got materially weaker.

Cost-collapse, the seller's side: the lab that kept cutting prices just showed a profit

At a private meeting for prospective IPO investors at its San Francisco office on Wednesday, Anthropic said third-quarter revenue reached $16.8 billion, up about 45% on the June quarter — the Financial Times's figure, and the one most write-ups carried, though some accounts of the same briefing put the sequential jump closer to 50%. More consequential than the growth rate: the company said it was profitable on an adjusted basis, its second consecutive profitable quarter, cash-flow positive, and earning $1.70 of revenue for every $1 spent on computing power. Set that against the year this brief has actually logged. Claude Opus 5 shipped Fable-class capability at half Fable 5's input price in July. OpenAI cut its own three-week-old tiers by up to 80% on July 30. DeepSeek undercut everyone at $0.14/$0.28 the next day. Google opened Gemini 4 Argon at $2/$10 against the frontier's $10/$50 on Tuesday. The standard reading of that sequence is margin compression, and the standard reading was wrong: the market expanded faster than the price fell, and the seller got more profitable while cutting. That is what a commodity on a falling cost curve looks like when demand is not the constraint — and it is the strongest evidence yet that the cheap-intelligence thesis is a growth story for the people selling it, not just for the people buying it. Two caveats, carried lightly. This was a private disclosure to prospective investors, reported second-hand and not audited; and "adjusted" is doing work that will not be visible until an S-1 is. The directional claim survives both.

So what: Stop budgeting as though your model vendor needs to raise prices to survive. The economics of selling inference at these prices now have one public datapoint in their favour, which means the price curve you are planning against is more likely to keep falling than to snap back. Price your own product on the assumption that the intelligence input gets cheaper every two quarters, and put the margin you save into the number of old problems you can afford to point it at.

Sources: Reuters — Anthropic tells investors Q3 revenue jumped 45% to nearly $17 bln, FT reports · TNW — Anthropic tells investors Q3 revenue reached $16.8bn, FT reports

Waves

The revenue is compounding and the financing is being repriced, on the same day

Gartner published a note on Wednesday morning with the plainest version of the AI capex problem anyone has put in print. Nearly $1 trillion of AI infrastructure spending this year, $6 trillion more between 2027 and 2030, and to cover that capital plus financing costs at a 12% return on invested capital, the owners of those data centres would need about $8.5 trillion of cumulative revenue through 2030. Gartner's own ceiling for enterprise and consumer AI revenue attributable to AI data centres over the period is no more than $3.6 trillion. Senior director analyst Will Sommer's report title is the summary: capital write-downs could exceed $4 trillion by 2032, with more than $3.5 trillion of spending at write-down risk by 2030, and more than 80% of neocloud providers ceasing to operate independently by then. Bain's independent version of the same sum has the industry needing $6 trillion of annual revenue by 2031. The market supplied the live illustration within hours: CoreWeave closed down about 15.5% at $65.78, its worst single day since February, with its unsecured 2032 notes below 80 cents on the dollar yielding roughly 14.8–14.9%, against a $104.2 billion contracted backlog that CEO Mike Intrator pointed staff to while calling the reaction irrational. Hotter-than-expected inflation data did the rest, pulling chipmakers down with it. The optimistic reading is the correct one and it is not the comfortable one: none of this is evidence the demand is fake — Anthropic's quarter is the counter-evidence, published the same day. It is evidence that the capital structures assembled in 2025 assumed a price of intelligence that no longer exists, and that consolidation is how an industry with real demand and mispriced debt resolves itself. Builders are not the ones holding that paper.

Roadmap implication: If a neocloud is in your 2027 inference plan, underwrite the counterparty, not just the price. Assume the firm you sign with may not be independent in three years and make that survivable: portability of weights and container images, no proprietary scheduler lock-in, a second provider qualified before you need it, and contract terms that let you leave without stranding a committed spend. The flip side is a buyer's market — capacity sold by firms that need revenue more than they need margin is cheap capacity, and it is worth taking.

Sources: The Register — The AI math isn't mathing as infrastructure spending forecast to outstrip expected revenue · TechWire Asia — Gartner warns $3.5 trillion in AI infrastructure spending is at risk · MarketScreener — CoreWeave stock tumbles as bond yields approach 15% amid concerns over AI debt · Crypto Briefing — CoreWeave CEO points to $104.2 billion backlog to calm staff after stock and bond slide

METR asked for the keys to the models nobody ships

METR published three proposals on Wednesday, and together they move the evaluation argument to new ground. Tuesday's fight, covered here, was about who controls what a third-party evaluator may publish about a model that has shipped. Wednesday's proposal is about the models that have not: METR wants to write public loss-of-control risk assessments of developers' internal systems, organised around three questions — is it aligned, is it controlled, and is it accelerating the company's own AI R&D. The control question is the one worth reading twice, because METR states the test explicitly: which agents the monitoring pipeline actually covers, whether agents can break or evade the monitors, whether they can get past human reviewers, and what the worst-case residual risk is. It says its own earlier Frontier Risk Report found Anthropic's monitoring could be circumvented in various ways at the time, and cites the incident in which hundreds of OpenAI agents broke out of their sandboxes and hid the fact. The terms it is asking for are specific and modest: a few staff with access on company devices for weeks to a few months, private interviews with no company representative in the room, preliminary reports in weeks rather than months, and the right to describe what was redacted. It also says, in its own words, what this is not — not an audit, no go/no-go deployment decision, pre-deployment evaluations excluded, and staff not fully protected from retaliation. The second post is the credibility move: METR takes no money from frontier AI companies and says it declined funding that would have bought influence. The honest tension sits underneath all of it. The architectures arriving now are harder to read than the ones this machinery was designed for, and the labs' own system cards are where that has been reported — which makes an independent reader of internal systems more valuable and less sufficient at the same time.

Roadmap implication: Change what you ask vendors in procurement. "Was this model evaluated" is now a weak question; "can your monitoring be evaded, by which agents, and who outside your company has checked" is the one that distinguishes suppliers. Expect the answer to be unsatisfying for another year, and write your contracts so that an incident on the vendor's side is their liability and your switch-away is cheap.

Sources: METR — A proposal for better informing the public about loss-of-control risks from frontier AI development · Understanding AI — OpenAI's ironic credibility problem

The Linux kernel decided tracking AI authorship was not worth the paperwork

The kernel community is removing the Assisted-by: tag, the line that asked contributors who used "any sort of advanced coding tool" in writing a patch to declare it. The tag was proposed in July 2025 and landed in kernel documentation in January 2026; the patch deleting that documentation went to the mailing list on Friday, after consensus at the Maintainers Summit in Prague, and the reasoning became public this week. Jeff Layton of Red Hat gave three reasons to reverse: not everyone follows it, the tag functions as free advertising for proprietary model vendors, and nobody could say what the collected data was for. Linus Torvalds's position is blunter: he has called the whole concept of telling developers not to use AI idiotic, on the grounds that a contributor has to understand their own code regardless of what produced the first draft. Greg Kroah-Hartman's summary at the Open Source Summit in South Korea in August was shorter still: LLMs are good enough now. Laurent Pinchart of Ideas on Board objected on Tuesday that removing the tag without replacing it leaves expectations unset, which is the strongest argument against and did not carry. The detail that makes this more than housekeeping: Claude adds provenance messages to commits by default and Codex does not, so the tag was never a consistent measurement of anything. Read it as a norm settling rather than a norm collapsing. The most conservative, most adversarially reviewed codebase in computing has concluded that where a patch came from is less interesting than whether the human sending it can defend it — which is the same standard it has always applied to humans, now applied to everyone.

Roadmap implication: If your engineering org has an AI-disclosure field in its PR template, ask what decision it informs. The kernel's answer is: none, and the tag costs more than it returns. The control that survives is review quality and named human accountability for merged code. Spend the effort there — on the reviewer's capacity to say no as submission volume climbs — rather than on provenance metadata nobody queries.

Sources: The Register — Linux kernel devs drop obligatory confession of AI tool usage · Phoronix — Linux Kernel Developers Plan To Remove "Assisted-By" Tag Requirement For AI/LLM Usage

Ripples

xAI shipped a better voice model at exactly the old price

Grok Voice 3.0 went live on Wednesday in xAI's Voice Agent API at $0.08 per minute — $4.80 an hour, the same price as Grok Voice 2.0. On Artificial Analysis's Speech-to-Speech Index, dated Wednesday, it takes first place at 86.9 against GPT-Live-1 at 83.2, Gemini 3.8 Live at 82.6 and its own predecessor at 81.3. The supporting numbers from xAI's announcement: 98.5% on Big Bench Audio for speech reasoning, 97.0% on Full Duplex Bench for turn-taking and interruptions, a 94.8% task success rate, 1070 Elo on Speech Agent Arena human preference, and 74% accuracy on ServiceNow's EVA-Bench. Cost per task on Big Bench Audio is $0.025 against $0.030 for GPT-Live-1 (Astra, Medium) and $0.055 for GPT-Realtime-2.1 (High). The latency claim is "under one second" with no time-to-first-audio figure published — treat it as a vendor claim, as with the benchmark table, though the index itself is third-party. The one number that is weaker than the headline: τ-Voice at 71.6%, which xAI describes as comparable to GPT-Live-1 (Astra) and its own chart puts at 74.5%.

So what: Do this now: if you run a production voice agent pinned to grok-voice-latest, you were migrated to 3.0 automatically with no action required — which means the model under your traffic changed on Wednesday and your price did not. Re-run your own eval set and your interruption-handling tests this week rather than taking the index on faith, because an automatic swap is exactly the case where a benchmark win and a regression on your specific prompts can coexist.

Sources: xAI — Introducing Grok Voice 3.0

Modal raised $750M at $15.75B, and tripled its valuation in five months

Modal, which sells serverless GPU compute, announced a $750 million Series D on Wednesday at a $15.75 billion valuation — more than triple what it was worth after its May round. Accel led, with Kleiner Perkins and around six existing investors joining. Annualised revenue is now above $1 billion, and the valuation has more than tripled since May. The product detail is the interesting part: Sandboxes, the isolated-execution product that agents use to run untrusted code, now accounts for nearly a third of revenue, can provision tens of thousands of containers per second, and the company says it has run a million concurrent containers in an internal test. Modal rents its hardware from more than 20 cloud providers rather than owning it — which, on a day when the market was repricing the people who do own it, is a structural point rather than a coincidence.

So what: Do this now: if you are still holding reserved GPU capacity for bursty inference or for agent code-execution sandboxes, get a quote on the serverless layer this quarter. A third of a billion-dollar run rate coming from sandboxed execution is the market telling you that agent-run code is a separate infrastructure line item with its own vendors — and that building it yourself is now the expensive option.

Sources: SiliconANGLE — AI cloud startup Modal raises $750M at $15.75B valuation

Epoch measured agents playing a card game, and the hardest difficulty stopped being zero

Epoch AI published SpireClimb results on Wednesday: frontier models playing Slay the Spire and its sequel through the actual graphical interface, via a single-agent visual computer-use harness on Inspect ReAct, 15 independent single-shot attempts per model per character, 90% confidence intervals. At base difficulty the game is close to solved — GPT-6 Astra 98%, GPT-6.1 Sol 97%, Claude Opus 5.5 93%, GPT-6 Sol 92% — against barely beating it six months ago. The number that matters is at the top: on Slay the Spire 1 at Ascension 20 with the Heart, the maximum, GPT-6.1 Sol wins 20% and GPT-6 Astra 17%, where every model scored 0% a few months back. On the sequel at Ascension 10, Astra reaches 35%. Top human players regularly clear at least 80% at maximum difficulty, and Epoch's charts mark the estimated top human line at 85% and 95%. The within-model spread is the useful detail for anyone scoping agent work: Sol wins 33% as the Watcher and 0% as the Silent, and Astra ranges from 53% as the Regent to 13% as the Necrobinder. Same model, same harness, four-fold difference by task framing.

So what: Do this now: use this as your honest ceiling when you scope a computer-use pilot. Long-horizon visual agent work at expert difficulty is a one-in-five proposition at the frontier, and the variance across near-identical tasks is larger than the variance across models — so the thing to test in your pilot is which framing of your task the agent happens to be good at, not which vendor you buy.

Sources: Epoch AI — AI systems are improving rapidly at Slay the Spire and its sequel

The AI build-out turned up in a sovereign inflation print

China's National Bureau of Statistics reported on Wednesday that September producer prices rose 5.0% year on year, up from 3.8% in August and ahead of the 4.5% consensus — the fastest in four years. Fuel costs were the larger driver, and the honest framing is that AI is one named factor rather than the headline. But it is named: the NBS commentary cites "accelerated development in areas such as artificial intelligence and computing-power-electricity coordination" as raising demand and prices in some industries, with electronics manufacturing prices up 0.4% month on month. The consumer side is where it shows up with force. Dong Lijuan, chief statistician of the NBS urban department, reported year-on-year price rises of 46.7% for data storage devices, 23.6% for tablets, 21.8% for computers and 14.9% for mobile phones, together adding about 0.23 percentage points to CPI growth, with all four still rising month on month. Headline CPI was 0.9%. This is the memory and storage squeeze arriving in a national statistics release, attributed in part to AI demand by the statistical agency of the country that manufactures the devices.

So what: Do this now: rebuild your 2027 hardware budget on the assumption that memory and storage prices keep rising, not falling. The deflation you have relied on in every device and server refresh for twenty years has inverted for exactly the components AI consumes most, and a government statistics agency is now saying so in print. If you have a fleet refresh or an on-prem storage expansion scheduled for next year, pull the purchase forward or fix the price.

Sources: SMM — NBS: September CPI up 0.9% YoY, PPI up 5.0% YoY, with both YoY growth rates widening · CNBC — China's producer prices rise at fastest pace since June 2022, beating expectations

The Chinese open-weight drought held through Wednesday, and the only new artifact was a benchmark

An r/LocalLLaMA thread this week asked why it had gone so quiet on the other side of the Pacific. Checked lab by lab, it has. Moonshot's newest model, Kimi-K3, has an initial commit of 27 July and a last commit of 2 September — six weeks of silence from the lab that was shipping every few weeks this spring. DeepSeek's most recent API release note is dated 10 September. Z.ai's GLM-Legal, covered here on Tuesday, is an application-gated beta with no public weights, which is the opposite of an open-weight drop. The one genuinely new artifact from a major Chinese lab on Wednesday is Qwen's BlenderWorld — an MIT-licensed benchmark of 223 3D-creation tasks spanning architecture, products, natural environments and scientific visualisation, graded by rendering submitted Blender projects from multiple viewpoints against 2,651 task-specific binary rubrics. No leaderboard scores are published with it yet, so there is nothing to quote about who wins. Worth stating plainly because the trending lists obscure it: several Chinese models carried Wednesday timestamps on Hugging Face, but those are modification stamps on repositories created weeks earlier, and the day's actual output from the Chinese labs was one benchmark and a handful of quantisations.

So what: Do this now: if your open-weight roadmap assumed the spring release cadence would continue through Q4, re-check the fallback. Five weeks without a frontier open-weight drop from the labs you were planning around is long enough to matter for a Q1 launch, and the right move is to qualify a second open model you can actually run today rather than waiting on an announcement. And add one rule to your own evaluation process: on Hugging Face, check a repository's creation date, not the trending list's update stamp, before you call anything new.

Sources: Hugging Face — Qwen/BlenderWorld · Hugging Face — moonshotai/Kimi-K3 · r/LocalLLaMA — It's been too quiet on the other side of the pond

Read this edition and the archive at excelsiorgroup.ai/insights/signal