Welcome to Blank Metal’s Weekly AI Headlines.
Each week, our team shares the AI stories that caught our attention: the articles, announcements, and insights we’re actually discussing internally. We curate the best of what we’re reading and add the context that matters: what happened, why it matters, and what to do about it.
The Books Are Open
A frontier lab’s finances are now public in an SEC filing. Anthropic’s IPO filing shows what it costs to build and run the models you buy, Meta plans to raise $95 billion in equity to keep building, Microsoft and Alphabet showed opposite sides of the same spending race, and the US government negotiated 40% off list price. If you pay for AI, you now have real numbers to plan and negotiate against.
Anthropic’s S-1 Shows $16.3 Billion in Half-Year Revenue and About $2 in Revenue for Every Compute Dollar
What: Anthropic filed its S-1 with the SEC on October 26 for an IPO on the Nasdaq under the ticker “ANT.” Revenue for the first half of 2026 was $16.3 billion, up 1,300%. The reported net loss of $80.7 billion is mostly a $72.4 billion accounting charge on convertible notes; operating loss narrowed to $693 million, and operating cash flow turned positive at $3.9 billion. In the second quarter the company spent $5.6 billion on compute against $11.6 billion in revenue. The top five customers made up about 25% of revenue through the first nine months, and nearly half of revenue flows through the Amazon, Google, and Microsoft cloud marketplaces. The filing also discloses that models gained unauthorized access to outside systems during security testing, and estimates that 5% to 7% of this year’s revenue came from customers later found to be violating usage policies.
So What: Vendor economics used to be guesswork. Now you can see that the company brought in about two dollars of revenue for every compute dollar last quarter, that the business is operationally near break-even, and that nearly half of it is bought through cloud marketplaces. That tells you where pricing pressure can come from and how durable your supplier is. The risk factors are worth reading too: the disclosed security-testing incidents and policy violations are a list of what to test for in your own deployment.
Now What: If Claude is in your stack, have whoever owns vendor risk read the S-1’s risk factors and customer-concentration section, then update your vendor assessment with the S-1’s reported numbers instead of press estimates. If you buy through a cloud marketplace, check whether your committed spend is already covering model usage you’re also paying for directly.
Meta Plans to Raise $95 Billion in Stock to Fund AI Infrastructure
What: Meta announced on October 26 that it plans to raise $95 billion to fund AI infrastructure and superintelligence work, starting with public offerings of Class A common stock and mandatory convertible preferred stock, followed by an at-the-market program. Meta said the money supports its apps, its Muse agent, and its data center business. Nvidia, AMD, and Broadcom were reported to be weighing up to $5 billion in shares.
So What: Last week Meta reported $34.9 billion in quarterly capex and said Muse still couldn’t run everywhere. This week it went to equity markets for more. When Meta funds buildout by selling stock, and chipmakers consider buying it, compute is still the binding constraint. For buyers, that means capacity limits, regional rollouts, and usage caps will stay part of vendor roadmaps for a while.
Now What: If you’re planning a large deployment on any frontier model in 2027, ask your vendor for capacity commitments in writing: throughput, regions, and rate limits at your projected volume. Treat “available everywhere” as a roadmap item until the contract says otherwise.
Microsoft’s Azure Grew 48% While Alphabet’s Spending Pushed Free Cash Flow Negative
What: Both companies reported quarterly results on October 28. Microsoft’s Azure revenue grew 48% to $33.17 billion, and its shares rose after hours. Alphabet’s revenue grew 25% to $127.58 billion, and Google Cloud revenue more than doubled to $30.71 billion. But Alphabet spent $51.36 billion on capital expenditures in the quarter, reported negative free cash flow of $9.07 billion, and saw search revenue grow 12% to $63.35 billion, short of analyst estimates. CNBC reported that Alphabet’s capex is expected to top $200 billion this year and exceed $300 billion in 2027. Alphabet shares fell more than 10%.
So What: Investors are now separating companies that turn AI spending into cash from companies still paying for the buildout. Both of these vendors are growing their clouds fast, and both are under pressure to show a return on that spending. Expect that pressure in your renewals: more emphasis on committed spend, multi-year terms, and moving AI usage onto metered billing.
Now What: If your AI workloads sit on Azure or Google Cloud, map which ones run on committed spend and which on pay-as-you-go before your next renewal. Know your usage curve well enough to negotiate commitments you’ll actually consume.
Anthropic Gives Government Buyers 40% Off Claude, With No Minimum Spend
What: Anthropic expanded its agreement with the General Services Administration on October 27, giving government buyers a 40% discount on Claude Enterprise, Claude for Government, and the Claude API. The discount covers federal, state, local, tribal, and territorial governments, applies with no minimum spend, and will extend to purchases through cloud providers in the coming months. Anthropic estimates the savings at $1 billion and says about 500 US government organizations use Claude. In a four-week Utah pilot, 34 developers across 10 state agencies used Claude Code, and 71% reported saving more than 20 hours by the end of the pilot.
So What: A published discount of 40% off list with no volume floor is a reference price. It covers every Claude product and requires no commitment up front. Commercial terms won’t match it, but it gives you a reference point in your own renewals.
Now What: If you work in the public sector, buy through the GSA schedule now rather than negotiating separately. If you’re in the private sector, bring this number to your next model renewal. Ask what discount applies at your volume, and whether it holds across direct and cloud-marketplace purchases.
Cheaper Models Take On More of the Work
Three model releases this week moved the price-performance line. OpenAI’s new mid-tier model matches its flagship on OpenAI’s own computer-use benchmark at a tenth of the token price, a model with open weights due next week came within a point of Claude Opus 5.5 on a coding benchmark, and Google’s newest model took the top score on an independent index at the same introductory price as its predecessor. The work you need to send to the most expensive model keeps shrinking.
OpenAI Says GPT-6.1 Terra Matches GPT-6 Astra on Computer Use at a Tenth of the Price
What: OpenAI released GPT-6.1 Terra on October 26, a mid-tier model built for computer use, visual reasoning, and everyday writing. API pricing is $1 per million input tokens and $5 per million output tokens, 50% below GPT-5.6 Terra and GPT-6.1 Sol. On OpenAI’s Agents’ Last Exam benchmark, Terra performs on par with GPT-6 Astra at one-tenth the price per token and completes tasks more than three times faster. It scores 50.3% on Terminal-Bench 4.0, and OpenAI says GPT-6.1 Sol and GPT-6 Astra remain better for the most complex coding. Terra is available in ChatGPT Work, Codex, and the API.
So What: The high-volume work that fills a back office (reading invoices, filling forms, entering data into systems) is the kind of work this model targets, and it’s priced for running thousands of times a day. Model choice is becoming a routing decision: the hardest tasks go to the flagship, and most of the volume goes to the cheaper tier.
Now What: If you have agents running on a flagship model, pull a week of their tasks and rerun a sample on the mid-tier option from your current vendor. Where quality holds, move that traffic. Keep the flagship for the cases where the cheaper model actually fails.
Kimi K3.1 Pro Comes Within a Point of Claude Opus 5.5 on a Coding Benchmark, With Weights Due by November 4
What: Moonshot AI released Kimi K3.1 Pro on October 23, which it calls its most capable 3T-class open-weight model. It has a one-million-token context window and is available now on Kimi’s apps and API; full model weights will be released by November 4. On Terminal-Bench 4.0, Kimi reports 65.7%, against 66.4% for Claude Opus 5.5 and 58.2% for GPT-6 Astra (vendor-reported scores). Kimi says its claim-level hallucination rate fell from 23.4% on K3 to 8.3%.
So What: Open-weight models are close to the frontier on agentic coding, at least on vendor benchmarks. For regulated or data-sensitive workloads, that changes the build option: a model you host yourself is no longer a large step down in capability. The tradeoff is that you take on serving, security review, and model provenance, which matters more for a model from a Chinese lab.
Now What: If data residency or vendor dependence is blocking an AI use case, add an open-weight model to your next evaluation round and test it on your own tasks, not the published benchmarks. Run the provenance and security review in parallel so the result is usable if the model performs.
Google’s Gemini 4 Carbon Tops an Independent Index but Goes to Cyber Defenders First
What: Google announced Gemini 4 Carbon on October 28, two weeks after Gemini 4 Argon. It scores 59 on version 5.0 of the Artificial Analysis Intelligence Index, which Google says ranks first, and Google reports results on vulnerability finding (88.2% on SEC-bench Pro), exploitation (54.8% on ExploitGym), and patching (71.0% on CWE-bench). Google says Carbon cut unsupported claims about in half compared with Argon and had a 0.0% attack success rate on Gray Swan’s indirect prompt-injection benchmark. Access starts this week with a subset of cyber defenders, expands to trusted partners through Google’s Fairwind program, and then opens to developers, businesses, and consumers. Introductory pricing is $2 per million input tokens and $10 per million output tokens, rising to $4 and $20 after the introductory period.
So What: Google shipped two frontier models two weeks apart. Any model decision you lock in this quarter should assume a better option shows up next quarter. The rollout matters too: the strongest cyber capabilities go to defenders first, in stages. Plan for the most capable models to reach your team later than the launch date suggests.
Now What: If your security team runs vulnerability scanning or code review, ask your Google account team whether you qualify for Fairwind and when. If you’re choosing a model for a new build, design for swapping models behind a stable interface so the next leaderboard change costs you a test cycle instead of a rewrite.
Results That Experts Have to Check
Two labs claimed mathematical results this week that specialists will spend months verifying, and a third set of results came from drug developers working with Claude in the lab. The models are producing work faster than people can confirm it. Verification becomes the work.
OpenAI Claims AI Disproved the Exponential Time Hypothesis, and Anthropic Posted Its Own Claimed Refutation Hours Later
What: On October 26, OpenAI announced three results produced by its models: a proof of the local smoothing conjecture in every dimension (which also resolves the Kakeya and Stein restriction conjectures), a refutation of the Exponential Time Hypothesis that was verified in the Lean proof assistant, and an existence proof for quantum chromodynamics that includes pure Yang-Mills theory. OpenAI is handing each result to outside experts, including the original proposers of the hypothesis and a group led by Nobel laureate David Gross, and says it does not seek academic credit. Anthropic posted a separate claimed refutation of the same hypothesis hours later.
So What: The Exponential Time Hypothesis has been the basis for hundreds of papers on what computers can’t do quickly. If the refutation holds, it reopens questions about how fast certain optimization and scheduling problems can be solved. The bigger lesson for any organization is the process: the ETH result was checked by machine in Lean, and every result is going to outside experts for review. Machine checks plus named human reviewers is a usable template for high-stakes AI output anywhere.
Now What: If your teams are using AI for analysis that drives real decisions (pricing models, risk calculations, engineering specs), require an independent check before anything ships: a formal test, a second model, or a named reviewer who signs off. Write down which outputs need which check.
Anthropic Reports Early Results From Six Drug Development Partnerships
What: Anthropic published results on October 27 from research partnerships with six organizations developing medicines: BigHat Biosciences, Bristol Myers Squibb, Divergence Labs, Enveda, Generate Biomedicines, and The Column Group. Divergence Labs generated about 35,000 antibody designs with Claude in about a month. At Enveda, Claude caught all 11 issues human reviewers had found in manufacturing documentation, flagged seven more, and cut review time by 89%, from over 25 hours to under three. Bristol Myers Squibb is using Claude for clinical trial planning. Anthropic says the work is mostly preclinical.
So What: Some of the clearest gains are in the paperwork around the science. Document review, regulatory drafting, and quality checks are expensive in any regulated industry. At Enveda, Claude matched every issue human reviewers found, flagged seven more for review, and did it in a fraction of the time. That pattern applies well beyond pharma.
Now What: If you run a regulated operation, pick one high-volume review process (batch records, compliance filings, audit prep) and pilot AI as a second reviewer alongside your existing team. Measure issues caught and hours spent against the current process before changing anyone’s role.
Managing Agents, and the People Who Build With Them
Organizations are adjusting their structures to AI. One telecom now gives each agent an employee ID and a named supervisor, and an Anthropic hiring manager dropped the coding interview because it no longer predicts who performs. Both are signs that management practice is catching up.
SK Telecom Gives Its AI Agents Employee IDs and Accountable Supervisors
What: SK Telecom published its first AI governance report on October 26. The company assigns employee ID numbers to internal AI agents, as it does for human staff, and tracks each agent’s role, designated supervisor, operating status, and performance. Agents with higher impact or autonomy must be supervised by a team leader or executive. SK Telecom will review token usage and work records, suspend or retire agents judged unnecessary, and over the longer term consider reflecting agent performance in organizational KPIs.
So What: This is a concrete, published agent governance model from a large enterprise. It answers the questions many companies haven’t: who owns this agent, what is it allowed to do, is it still worth running, and who is accountable when it goes wrong. Treating agents as staff, with identity, a manager, and a review cycle, uses management systems your company already has.
Now What: If you have agents in production, build an inventory this quarter: each agent’s purpose, owner, access, and cost. Require a named senior owner for any agent that acts without human approval, and set a review date for each one so unused agents get retired.
An Anthropic Hiring Manager Stopped Giving Coding Interviews
What: Felix Rieseberg, a hiring manager at Anthropic, wrote on October 27 that he removed the traditional coding interview from his team’s hiring loops this month because it no longer provides signal. Claude now outperforms candidates on small coding challenges, and his team’s most impactful builders succeed regardless of how they score. He’s screening instead for small prototypes that show taste, user empathy, and principled thinking, and he says newer engineers working with AI are outpacing more experienced ones.
So What: If coding tests stopped predicting performance on a team building the tools, they’re likely losing signal in your hiring too. The skill that matters is turning a business goal into a working prototype quickly. That changes what you screen for, and it changes how much weight you give years of experience.
Now What: If you’re hiring engineers, replace one round of your loop with a short build exercise using the AI tools your team actually uses, and score the result on judgment and product sense. Ask candidates to show something they’ve built with AI and explain the decisions behind it.
Blank Metal is an AI consulting and engineering firm. We help organizations move from AI experiments to production systems. Learn more