“AI” is now used as a label for everything from simple automation to systems that generate text, code, images, and decisions. For boards, the first job is not to become technical—it is to build a shared vocabulary so strategy, risk, and accountability can be discussed without hand‑waving.

Frictionless AI retrieval creates a dangerous illusion: if Unpaywall found a legal open-access copy and Claude summarized it, the workflow must be compliant. It may not be. Organizations using Claude or similar tools for scholarly workflows remain responsible for lawful access, license compliance, data protection, and platform terms—even when OA discovery tools and AI vendors make retrieval feel automatic.

Open access solved a reader-access problem: paywalls no longer block qualified researchers from reading scholarship. It did not automatically solve a creator-payment problem—and AI retrieval at scale may shift economic value toward intermediaries unless licensing and funding models explicitly account for new uses. When AI systems ingest OA literature, do creators and publishers actually get paid?

The compliance line in AI-assisted scholarly retrieval is not drawn at “open versus closed.” It runs between locating publisher-authorized open-access copies and any practice that bypasses technical or contractual access controls, exceeds license scope, or violates site or API terms—even when an AI system could technically retrieve the bytes. Here we map where lawful OA ends and circumvention, scraping, and policy violations begin.

When teams wire Claude or another AI assistant into scholarly research workflows, the first technical question is usually practical: can we use Unpaywall to find full-text papers? The first compliance question is harder: does discovery through an open-access index grant permission to copy, store, summarize, or commercialize what we retrieve? Unpaywall can lawfully help locate publisher-authorized or repository-hosted open-access copies of scholarly articles, but using that discovery in an AI retrieval workflow still leaves separate, and often stricter, questions about copying, terms of service, licensing, and downstream reuse.

Over the past eight posts, this series has examined the 2026 AI token economy from six distinct angles: the Uber budget collapse, the physics of context scaling, recursive agent loops, per-minute pricing disruption, KV cache optimisation, infrastructure power constraints, and the local inference break-even. Each post was a close-up on a specific failure mode or opportunity. This final post is the wide-angle view — a synthesis of the full series into a governance framework that translates individual insights into organisational practice. The thesis is simple: the era of “tokenmaxxing” — deploying AI at maximum capability without cost discipline — is over. The organisations that will thrive in 2027 are those that implement economic governance over their AI stacks before their next budget cycle, not after.

Every post in this series has examined a different dimension of API cost: token pricing, context scaling, agentic multiplication, per-minute billing, cache optimisation, and infrastructure constraints. The implicit assumption throughout has been that API inference is the only option — that your choice is which provider, which model, and which optimisation technique to apply within the API billing model. In 2026, that assumption requires re-examination. Small Language Models (SLMs) combined with 4-bit quantisation have reached a capability and cost profile that makes local inference economically rational for a well-defined and growing class of enterprise workloads. Understanding when to bypass the API entirely is now a first-order strategic decision, not a research-stage exploration.

Every discussion of AI cost in 2026 eventually arrives at the same upstream constraint: electricity. The token prices on every API pricing page, the per-minute rates, the per-seat subscriptions — they are all downstream of a physical fact that no software optimisation can dissolve. Training and running large language models requires power at a scale that is straining the capacity of data centres, national grids, and the global supply chains for the hardware that converts electricity into inference. Gartner’s forecast of $1.37 trillion in AI infrastructure spending by 2026 is not a number about software or services — it is primarily a number about construction, cooling, and electrical generation. Understanding this layer is essential for any CTO who wants to reason accurately about the medium-term trajectory of AI costs.

In the early years of cloud computing, the insight that transformed infrastructure economics was simple: storing data once and serving it many times from a distributed object store was orders of magnitude cheaper than recomputing or re-fetching it on every request. S3 became the canonical implementation of that insight. In 2026, the equivalent insight in AI inference is server-side KV cache management — and the organisations that have operationalised it are reporting 60–90% reductions in input token costs for workloads with stable, repeating context. This is not a niche optimisation. For any production AI system with a consistent system prompt, a shared knowledge base, or a high-volume API, prompt caching is the highest-ROI infrastructure investment available in the current AI cost landscape.

The token has been the unit of account for AI inference since the first public OpenAI APIs launched in 2020. Every pricing page, every cost model, every engineering estimate in the industry has been denominated in tokens per million. In 2026, Google disrupted that convention with the Gemini Live API, priced not at the token level but at $0.005 per minute of audio interaction. This is not a minor pricing variant — it is a structural challenge to the assumptions that underpin every real-time AI application budget. Understanding when per-minute pricing is economically superior to per-token pricing, and when it is not, is now a required competency for any engineering leader deploying AI at scale.

A software bug that causes infinite recursion terminates with a stack overflow. A token bug — an agentic AI loop that recurses without a termination condition — terminates with a billing invoice. In 2026, as autonomous agents displaced simple chat completions as the primary AI interaction pattern, organisations discovered that the economics of agentic systems are fundamentally different from those of single-shot inference. Anthropic’s decision to move Claude agents onto metered billing across all subscription tiers was not a product update. It was a signal that the industry has reached an inflection point where agent economics require the same governance discipline as cloud infrastructure.

This series connected a simple strategic idea—reducing lock‑in and increasing control—to how modern EU rules ask you to prove security, resilience, data respect, and product discipline. Open source is a means, not a certificate. The outcome regulators care about is operational: defensible governance, tested recovery, traceable software, and honest data handling.