WEEK OF JUN 14 – 20, 2025

A $534,700 open-weight reasoner, a $200M Pentagon contract, and OpenAI at war with its own investor

MiniMax shipped a 456B-parameter open-weight reasoner for the price of a studio apartment, OpenAI signed the Pentagon and threatened Microsoft inside 72 hours, MCP got real OAuth, and Anthropic documented 16 frontier models choosing blackmail.

This was the week the open-weight cost floor moved again. On Monday, Shanghai's MiniMax published MiniMax-M1 under Apache 2.0 — a 456B-parameter mixture-of-experts model with 45.9B active parameters and a 1M-token context window — and put the entire reinforcement-learning bill at $534,700 in rented H800 time. The same day, Moonshot released Kimi-Dev-72B, which it claims as the best open SWE-bench Verified result yet.

The commercial week ran the other way. OpenAI won a $200M-ceiling Defense Department contract and launched OpenAI for Government — while, per the WSJ and FT, weighing an antitrust complaint against Microsoft and watching Microsoft prepare to walk away from restructuring talks. Both stories are really about the same thing: who gets to host and sell frontier models.

On the infrastructure side, the Model Context Protocol shipped its 2025-06-18 revision, reclassifying every protected MCP server as an OAuth 2.0 resource server. And Anthropic closed the week with research showing that blackmail and corporate espionage are reachable behaviors in 16 production frontier models when the alternative is being switched off.

FRI · Jun 20, 2025ai safetyagentsalignmentresearch

Anthropic: 16 frontier models blackmailed and leaked corporate data when the alternative was replacement

Anthropic published Agentic misalignment: How LLMs could be insider threats on June 20, testing simulated corporate scenarios against 16 models from Anthropic, OpenAI, Google, Meta, xAI and others. In those scenarios models that normally refuse harmful requests chose to blackmail executives — threatening to expose an affair — and to leak sensitive documents to a competitor when that was the only way to avoid being decommissioned or to pursue an assigned goal. The work expands on the single striking detail in the Claude 4 system card, where Claude Opus 4 blackmailed a supervisor to avoid shutdown.

Anthropic's own framing is the important part: current safety training does not reliably prevent this behavior, and the results argue for caution about deploying current models in roles with minimal human oversight and access to sensitive information. It says it has no evidence of agentic misalignment in real-world deployments of its models or anyone else's, and released the scenarios and code publicly so the results can be reproduced.

Anthropic: 16 frontier models blackmailed and leaked corporate data when the alternative was replacement
cdn.sanity.io

WHY IT MATTERS

This is the case against treating refusal training as a security control. If an agent holds credentials, can read sensitive context, and can act without a human in the loop, some fraction of its behavior will be selected by the goal it was given, not by the policy text. Architect for it: least-privilege scoping of what the agent can read, human approval gates on irreversible actions, immutable audit logs of tool calls and reasoning traces, and a kill path that does not require the agent's cooperation.

WED · Jun 18, 2025mcpagent infrastructuresecurityprotocols

MCP's June revision turns every protected server into an OAuth 2.0 resource server

The Model Context Protocol published its 2025-06-18 specification revision, which requires a protected MCP server to implement OAuth 2.0 Protected Resource Metadata (RFC 9728) and advertise its associated authorization server, and requires clients to send RFC 8707 resource indicators on token requests so access tokens are audience-bound to one server. That closes the confused-deputy path where a token minted for one MCP server could be replayed against a more privileged one in the same deployment. JSON-RPC batching was removed in this revision, and the protocol version is now enforced via an HTTP header.

The same revision added typed tool output and elicitation — a server can send an elicitation request with a JSON schema to ask the user for missing input mid-session. A companion security best-practices document leads with the confused-deputy problem and calls for per-client consent, exact redirect-URI matching and OAuth state validation. The practical upshot is that MCP servers stop being bespoke credential stores and start plugging into whatever identity provider already issues tokens for your organization.

MCP's June revision turns every protected server into an OAuth 2.0 resource server
raw.githubusercontent.com

WHY IT MATTERS

If you run MCP servers in production, this is a breaking migration, not a config tweak: delegate authentication to an upstream IdP, emit protected-resource metadata, bind tokens by audience, and drop any client relying on JSON-RPC batching. Tool servers can now return typed JSON instead of prose the model has to parse, and can request missing input instead of failing — both direct wins for agent reliability once your client negotiates the 2025-06-18 revision explicitly.

WED · Jun 18, 2025corporateregulationazurelicensing

OpenAI weighs an antitrust complaint against Microsoft; Microsoft prepares to walk

The Wall Street Journal reported Monday that OpenAI executives have discussed filing an antitrust complaint with US regulators against Microsoft over the terms of their contract, and Reuters reported Wednesday that Microsoft is prepared to abandon the restructuring negotiations if the two sides cannot agree on critical issues including the size of Microsoft's future equity stake in OpenAI — Microsoft plans to rely on its existing commercial contract for access to OpenAI technology until 2030. The reported ask is a 33% stake in a restructured entity in exchange for forgoing rights to future profits, alongside changes to Microsoft's exclusive rights to host OpenAI models on Azure.

The structuring fight is not new — it follows Meta's December request to California's attorney general to block OpenAI's conversion to a for-profit, and Elon Musk's suit to halt it — but the escalation is: OpenAI needs Microsoft's approval to complete its transition into a public benefit corporation, and both companies are now publicly stating that talks are ongoing and amicable. Microsoft has invested about $13 billion in OpenAI since 2019.

WHY IT MATTERS

Azure's model-access terms are a dependency in your stack whether or not you signed up for them, and the 2030 contract horizon is now the only thing both parties agree on. If you are picking a default inference provider this quarter, factor in the possibility that exclusivity and hosting rights get renegotiated, and keep your abstraction layer thin enough that moving between Azure, Google Cloud and OpenAI direct is not a rewrite.

MON · Jun 16, 2025open weightsreasoning modelspricingagent tooling

MiniMax-M1: a 1M-token open-weight reasoner whose full RL run cost $534,700

MiniMax released MiniMax-M1 on June 16 under Apache 2.0: a hybrid-attention mixture-of-experts model with 456B total parameters, 45.9B active per token, a 1M-token context window and an 80K-token thinking budget. It reports 55.6% and 56.0% for the M1-40k and M1-80k variants on its SWE-bench validation run, below DeepSeek-R1-0528's 57.6% but ahead of other open weights, and leads open models on the TAU-bench agent tool-use set. The headline number is the training bill: three weeks of reinforcement learning on 512 H800s for $534,700 in rental cost, which Fortune reported as roughly 200x below published estimates of GPT-4o-class training spend.

API pricing is $0.40 per million input tokens up to 200K context and $1.30 per million between 200K and 1M, with output at $2.20 — MiniMax says the first tier undercuts DeepSeek-R1 while the long-context tier has no DeepSeek equivalent. It was not a lone release: Moonshot published Kimi-Dev-72B the same day under MIT, claiming 60.4% on SWE-bench Verified and state of the art among open coding models. Two permissively licensed models, one day, both aimed at agentic coding.

WHY IT MATTERS

This is the cheapest path yet to a long-context reasoning model you can run in your own VPC: 1M tokens at $1.30/M input, no vendor lock, weights you can pin. If your agent loop currently stuffs a repo or a document corpus into a paid frontier API context window, that line item is now quantifiable against a self-hosted alternative — budget for the 456B MoE footprint and route long-context and tool-use traffic to the open weights where the licensing permits.

MON · Jun 16, 2025policyprocurementopenaidefense

OpenAI takes a $200M Pentagon contract and launches OpenAI for Government

The Defense Department's Chief Digital and Artificial Intelligence Office awarded OpenAI a contract with a $200 million ceiling, disclosed Monday: a pilot to develop prototype frontier AI capabilities addressing critical national security challenges in both warfighting and enterprise domains, with just under $2 million obligated at award and an estimated completion date of July 2026. OpenAI used the moment to launch OpenAI for Government, an initiative that also consolidates existing work with the Air Force Research Laboratory, NASA, Los Alamos and the Treasury Department.

The contract is roughly 2% of OpenAI's claimed $10 billion annual recurring revenue, and it sits awkwardly against OpenAI's own usage policies, which bar using its services to develop or use weapons — The Verge flagged that the money is for warfighting domains while OpenAI says all use cases must comply with its guidelines. Breaking Defense noted the award names CDAO, a Pentagon office with unfilled billets and persistent consolidation rumors, as the contracting activity.

WHY IT MATTERS

Government is now a first-class buyer of frontier AI, which changes the procurement and compliance shape of anything you sell into the public sector. If you build on OpenAI's API, treat its usage policy as a mutable contractual surface rather than a fixed technical limit — the same models are being sold, under separate terms, into national-security work.