Home AI News

AI News Roundup for September 10: The Meter Is Now Visible

The Pentagon wrote refusal rate into a contract, Amazon got paid $4B to buy Qualcomm chips, and OpenAI published the receipt for one theorem.

A brushed-metal analog gauge mounted on a server rack in a dark data center corridor, its needle lit by cyan light

Five stories crossed my feed since Tuesday, and the coverage filed them under five separate beats: defense, semiconductors, mathematics, cloud pricing, creative tools. Read together, three of them are the same story, and I did not see anyone connect them.

This was the week the industry stopped hiding what a unit of AI work costs. Every writeup I found treated OpenAI’s proof as a math story and Google’s spending caps as a billing footnote. Put the compute bill next to the spend cap next to Amazon’s warrant and the shape is hard to miss: you are not buying software with an AI feature bolted on. You are buying metered work, and the meter finally has a display.

The Pentagon Asked OpenAI for a Model That Refuses Less Often

The Intercept sued for these documents and won. Its reporting on more than 400 pages of contract paperwork, obtained through a Freedom of Information Act lawsuit with Legal Advocates for Safe Science and Technology, shows Anthropic, Google, OpenAI and xAI each signed deals worth up to $200 million with the Department of Defense, originally in July 2025. The line that matters is a definition:

“OpenAI Mission Models” refer to OpenAI models that are designed for national security use cases and have minimal refusal rates.

That phrasing appears in a version of the contract signed in February, according to The Intercept’s separate account of the OpenAI paperwork, and OpenAI spokesperson Nate Evans told the outlet the company “has never agreed to contract language requiring ‘minimal refusal rates,'” describing it as draft language that did not survive into the executed agreement.

Take that denial at face value and the story holds anyway. Somebody at the Pentagon wrote refusal rate into a procurement document as a specification, which means both sides of the table understand it as a dial rather than a property of the model. The surrounding obligations are just as telling: the contracts commit these companies to run tabletop exercises, brief the military on adversary tactics, and perform what the paperwork calls risk forecasting and threat ideation exercises about the dangers of their own products.

Anthropic is the one that pushed back, refusing to sign amendments that would put its models on classified networks without written prohibitions on domestic surveillance and autonomous weapons. The Intercept reports that Defense Secretary Pete Hegseth designated the company a supply chain risk in March over it, and that a federal judge overturned the ban in August.

Matters. What I actually think: safety behavior is a contract term now, not a model property, and anyone building on a frontier API should stop describing their vendor’s guardrails as though they were physics. Anthropic absorbed a supply chain risk designation to keep two lines in a contract. That is the most informative thing any lab did this quarter, and it is worth more than every safety blog post published alongside it.

Amazon Is Being Paid $4 Billion to Buy Qualcomm’s Chips

Qualcomm announced a multi-generation collaboration with Amazon on Tuesday covering custom AI inference silicon and optical connectivity reaching 1.6 terabits per second for AWS data centers. CNBC reported that Qualcomm issued Amazon warrants for 25 million shares at $161.26 each, roughly $4 billion of stock, and that Qualcomm shares climbed about 10% on the news.

Read the direction of payment. Qualcomm is not being paid to supply. Qualcomm is paying Amazon, in equity, to become a customer, with the warrant vesting against as much as $60 billion of purchases over a ten-year term. Nvidia does not do this. Nvidia has a waiting list.

Matters, especially if you rent inference. A warrant that vests against purchase orders is a commitment to steer workloads onto one instance family for a decade. If you run inference on AWS, the cheapest per-token option available to you in 2028 will be cheap because of this deal, and it will not be portable. Price your exit now, while it is still hypothetical and costs you nothing but an afternoon.

OpenAI’s Proof Took 10,000 Agents, 88 Hours and Several Million Dollars

OpenAI published a claimed proof of finite-time blowup in the three-dimensional Navier-Stokes equations, produced by an unreleased internal model. Quanta Magazine’s account puts the run at roughly 10,000 autonomous agents exchanging close to five million messages over 88 hours, with a further 17 hours to verify the result formally in Lean, at an estimated cost of several million dollars.

The headline nearly everywhere was that AI solved a Millennium Prize Problem. The Clay prize has not been awarded, independent mathematicians are still working out whether the proved statement meets the criteria, and there is a credit fight running underneath the whole thing: NYU’s Tristan Buckmaster and Anthropic researcher Levent Alpöge had been working the same territory for close to a year, and Buckmaster has said OpenAI pressed him to drop Alpöge from authorship, which OpenAI’s researchers deny.

Princeton’s Charles Fefferman told Quanta he was thrilled the problem was solved and pointed credit toward Diego Córdoba and Luis Martínez-Zoroa, whose techniques both teams built on. That is the healthiest sentence in the episode.

Marketing, wrapped around one real number. The proof may well hold, and the Lean verification is the only reason it deserves serious attention, which is the same argument I made about Anthropic’s Fermat formalization earlier this week. A checker that does not care who is watching beats any amount of confidence from the model that wrote the thing. But the reportable fact for operators is not the theorem. It is that a frontier lab spent millions of dollars and 88 hours of ten thousand parallel agents to produce a single result, and then told us the number. Every vendor pitching you unbounded agent parallelism this quarter is selling a technique whose one public benchmark cost more than your engineering team does.

Gemini Enterprise Will Pause Your Agent Mid-Task

Google added a pay-as-you-go edition of Gemini Enterprise with no seat fee and no base subscription, billing tokens, compute, memory and storage at standard rates, plus project-level spending caps. TechRepublic’s writeup of the change notes discounts of 10% for a one-year committed spend and 20% for three years.

The cap is the part to read closely. Set a monthly budget and Google fires alerts at 50%, 80% and 100%, then automatically pauses the agent’s API calls once the ceiling is reached.

Breaks your stack. An agent halted at 100% of budget is not a billing event, it is a partial failure in the middle of a multi-step job, and almost nobody’s agent code has a resume path for that. If you adopt this, the cap needs a handler that checkpoints state and pages a human, not a retry loop that burns next month’s budget rediscovering where it stopped. Google shipping a shutoff valve at all is an admission that agent bills are outrunning what seat pricing can absorb, which is the same signal as OpenAI’s compute receipt above, denominated in a different currency.

ChatGPT Images 2.5 Splits the Image API in Two

OpenAI shipped ChatGPT Images 2.5 on Tuesday, claiming generation up to 50% faster, better preservation of subjects from reference photos, and more reliable edits across multiple turns, alongside Sketch, Templates, image comments and prompt sharing in the product itself. For builders the relevant part is the API, which now forks into GPT-Image-2.5 Flare for speed and quality and GPT-Image-2.5 Sunburst for precision work at longer generation times.

Breaks your stack, in my case literally. Every hero image on this site, including the one at the top of this post, comes out of an OpenAI image model routed through Kie, so a two-model fork is a routing decision I have to make rather than a release note I get to skim. The claim I care about is reference-photo subject preservation, because our house rule is that a hero about a named person gets grounded on a real reference photo rather than conjured from a text prompt, which is the difference between that person and a generic look-alike. If Sunburst holds a likeness better, it earns the slower render on portraits and earns nothing on the other eighty percent of images.

What I Am Changing in My Own Stack

I am benchmarking Sunburst against our current image path this week on exactly one axis, likeness against a supplied reference photo, and ignoring every other claim in the release notes until that one resolves.

The broader move is duller and more important. Three of today’s five stories are the same admission arriving from three directions. Google built you a shutoff valve. Amazon got paid to commit to a decade of silicon. OpenAI published the receipt for one theorem. If your 2027 planning still treats AI as a per-seat line item, your vendors have already moved on without you.