AI Is Breaking the Contracts That Made the Internet Work

Horacio Ontiveros Por Horacio Ontiveros
AI Is Breaking the Contracts That Made the Internet Work

Oracle quietly cut its free tier in half. Tailwind lost 80% of revenue at peak popularity. Stack Overflow sells its data to the AIs that destroyed it. Something structural is changing — not in the technology, but in the implicit economic contracts that made the internet work.

Artificial intelligence isn't replacing jobs or destroying companies the way apocalyptic narratives predicted — it's doing something subtler and more profound: it's breaking the implicit economic contracts that made the internet work for 30 years. The free tier as an acquisition model. Advertising funded by human attention. Open source sustained by organic traffic. Technical employment as replaceable commodity. All of these contracts are being renegotiated without anyone asking permission.

Oracle and the end of the generous free tier

In June 2026, Oracle quietly cut its Ampere A1 Always Free tier from 4 OCPUs and 24GB of RAM to 2 OCPUs and 12GB — exactly half. No public announcement. No official communication. No email to affected users. They just updated the documentation and waited for someone to notice.

People noticed on Reddit. User reports confirming contact with support established that instances exceeding the new limits will be shut down unless migrated or the account is upgraded to a paid tier.

This isn't just a pricing change. It's the signal that the "free tier as a hook to convert you into a paying customer" model is reaching its limits. For years, OCI offered absurdly generous free resources because the acquisition cost of an enterprise customer justified subsidizing thousands of free accounts. AI changed that calculation — infrastructure costs rose and patience with free tier arbitrage ran out.

The cost you can't calculate: token opacity

If you've ever tried to estimate how much a month of AI API usage is going to cost you, you already know what I'm talking about. Models count tokens differently from each other. System prompts consume tokens that don't always appear in the visible counter. Conversation context accumulates tokens on every turn. Images have their own metric. Embeddings have another one.

This isn't an accident. The complexity in AI service pricing works exactly like bank fees or telecom contracts: it makes it hard to compare providers, hard to budget accurately, and hard to notice when costs spiked until the invoice already arrived. (Ironically, this post was written with AI)

The consequences for product teams are real: real-time cost uncertainty makes architectural decisions extremely difficult. How many tokens does my RAG pipeline consume per query? How much does maintaining long context cost versus summarizing? Is it worth using a more expensive model or scaling with the cheaper one? These are questions that should theoretically have clear answers and in practice require weeks of experimentation to approximate.

Technical employment: the chaos of the broken promise

In late 2022, when ChatGPT exploded in mass adoption, many companies drew a premature conclusion: developers would be partially replaceable in the short term. They froze hiring, restructured teams, and adjusted budgets based on that premise.

Two years later, the reality is more nuanced. AI radically changed the profile of technical work — but didn't eliminate it. What it did generate was a period of chaos in the labor market where companies didn't know how many developers they needed, with what skills, or how to structure teams around the new tools.

Stack Overflow's 2025 developer survey illustrates it well: 84% of developers use AI tools in their daily work, but only 3.1% highly trust the output. 46% actively distrust AI accuracy. The tool is omnipresent and human judgment remains indispensable to validate it — exactly the opposite of what the most alarmist headlines predicted.

Stack Overflow and the ironic business of selling your data to whoever destroyed you

In December 2025, Stack Overflow recorded 3,862 questions in the month — the same volume it had in 2008, when it had just launched. At its 2014 peak, it received more than 200,000 monthly questions. A 78% drop in question volume in a single year.

But here's the irony: Stack Overflow's revenue grew to $115 million in its last fiscal year. How? By selling access to its historical database to the same AI companies that, having been trained on that content, destroyed the traffic flow that sustained the original advertising model.

ChatGPT trained on Stack Overflow's data. Then it answered the questions developers would have gone to Stack Overflow to find. Stack Overflow now sells its data catalog to OpenAI and others. The complete cycle of value extraction without return to the original creator — and the only exit it found was to become a supplier to the same system that hollowed it out.

Tailwind CSS: the world's most popular framework that almost couldn't make payroll

In January 2026, Adam Wathan, founder of Tailwind CSS, laid off 75% of his engineering team. Three of four engineers. The company was left operating with three cofounders, one engineer, and a part-time employee.

The reason: revenue fell nearly 80% while framework usage reached all-time highs. 75 million monthly npm downloads. 51% adoption in CSS projects according to State of CSS 2025. The most popular framework in its category in history — and the business behind it almost couldn't make payroll.

The problem is structural: Tailwind monetized through traffic to its documentation. Developers would arrive searching "how to center a div in Tailwind," find the answer, and incidentally see the Tailwind UI banner ($299 lifetime license). That was the entire acquisition funnel.

That funnel is dead. Now the developer asks Cursor or Claude Code "center this div with Tailwind" and the IDE answers directly. They never open a browser. They never see the banner. Documentation traffic dropped 40% since 2023 — and the revenue decline was twice as proportional because the visitors who were lost were exactly the ones who converted.

The brutal paradox: Wathan rejected a PR proposing to add an llms.txt endpoint to make the documentation more readable for AI models — because making it easier for AI to consume would accelerate exactly the problem that's destroying the business. The AIs already know Tailwind by heart. They don't need the llms.txt. But providing it would have been symbolically suicidal.

Cloudflare Pay per Crawl: the first attempt at a new contract

In July 2025, Cloudflare launched Pay per Crawl in private beta — and with it, the first serious attempt to create a new economic contract between AI models and content creators.

The mechanism is elegant: any site behind Cloudflare can configure a rate per crawl. AI bots that want access must authenticate with an Ed25519 cryptographic key pair and Cloudflare automatically charges them, distributing the revenue to the publisher. If the bot doesn't want to pay, it doesn't get access. The HTTP response is a 402 — Payment Required.

Worth clarifying: there is no cryptocurrency involved in Cloudflare's product. The x402 protocol and discussions about smart contracts are conversations from the broader ecosystem, not the actual implementation. Cloudflare acts as a traditional payment intermediary. The idea of automatic crypto micropayments exists, but this isn't it.

The numbers that justify why this matters: OpenAI has a crawl-to-referral ratio of around 1,700:1. Anthropic's is 73,000:1. That means for every user Claude or GPT sends to a site, they've consumed tens of thousands of pages from that site. For comparison, Google has a ratio of about 14:1 — it consumes and returns traffic. AI models consume and return nothing. In March 2025, more than 26 million AI crawls bypassed robots.txt.

Pay per Crawl isn't a complete solution — current rates are micropayments that can hardly compensate for the revenue impact Tailwind describes. But it's the first concrete mechanism that redefines the contract: if you want to consume someone else's content to feed your model or answer your users' queries, there's a price for access.

What's really changing

These aren't isolated cases of companies that failed to adapt. They're symptoms of the same phenomenon: the internet was built on implicit contracts that assumed the visitor was human, that human attention was the exchangeable commodity, and that free access to information was reciprocal.

AI models broke all three assumptions simultaneously. Visitors can now be bots. Attention no longer passes through the site. And access to information is one-sided — models take everything and return nothing to the ecosystem that fed them.

What's coming isn't the end of the internet, but it is the end of several of its economic models. The free tier subsidized by future conversion expectations has an expiration date. Advertising funded by human traffic does too. Open source sustained by organic discovery, also.

What Cloudflare is building — however imperfect — is the signal that the next chapter is an internet where access to content has a price, even for machines. And where creators of quality content will need to find ways to charge those who benefit from it without returning anything in exchange.

The question that remains open: who has enough leverage to make that contract stick?

Conversation

Log in to join the conversation.