OpenAI’s recent acquisition of OpenClaw wasn’t just about talent or technology. They bought a distribution channel—a powerful revenue pipeline that was funneling massive API usage and revenue to a competitor, Anthropic. OpenClaw, an autonomous agent platform, defaults its model provider hierarchy to Anthropic’s Claude models, which dominate the token consumption that drives API revenue.
OpenClaw isn’t your average chatbot; it’s a relentless token furnace. It integrates deeply with email, calendars, browsers, and messaging apps, running multi-step workflows with persistent memory. This architecture means it burns through tokens at astonishing rates—sessions can balloon to hundreds of thousands of tokens, and background “heartbeat” checks alone can cost hundreds of dollars per week per agent. Light users spend tens of dollars monthly on API calls, but heavy users can rack up thousands, even tens of thousands, in a single month. This is a quantum leap beyond chatbot-era economics—it’s not incremental, it’s orders of magnitude more expensive.
Those tokens translate directly into revenue for model providers. OpenClaw’s default configurations overwhelmingly favor Anthropic’s Claude models, driving the bulk of this enormous token spend to Anthropic’s API. With OpenClaw’s explosive growth—over 180,000 GitHub stars and an estimated 50,000 to 200,000 active users—this translates to tens of millions, potentially over a hundred million dollars in annualized API revenue flowing to Anthropic. For OpenAI, facing billions in projected losses and intense competition, that’s a revenue leak they couldn’t ignore.
The irony is sharp. Steinberger built OpenClaw explicitly for Claude, even naming it after the Claude model. He was essentially subsidizing Anthropic’s revenue by running high-cost API calls on his own dime. Anthropic’s response was to send a cease-and-desist over the project’s name, alienating the very community driving their growth. Within weeks, OpenAI swooped in, acqui-hiring Steinberger and effectively capturing the most powerful agent ecosystem driving revenue to their competitor.
This acquisition wasn’t just about adding a brilliant engineer or community goodwill. It was about controlling the defaults in agent platforms, which dictate model usage and thus revenue flows. Defaults matter. Just like browser search engine defaults shaped billions in ad revenue, agent platform defaults will shape trillions of tokens in API spend. Autonomous agents running 24/7 with complex workflows generate hundreds of millions to trillions of tokens monthly. Whoever controls that agent layer controls the revenue.
This is the start of a broader pattern: autonomous agents are becoming the new distribution layer for AI models, much like mobile apps became the distribution layer for cloud infrastructure in the 2010s. Apps created persistent compute demand, driving massive cloud revenue. Agents now create persistent token demand that compounds with each new user and integration. The scale is breathtaking—over 50 trillion tokens processed daily across the market, with agents accounting for nearly half. The economics of model defaults in agent platforms will be the new battleground.
For CTOs evaluating agent infrastructure, this means your choice of default model provider isn’t neutral—it’s a financial commitment. The token economics of agents dwarf chatbot-era costs. A fleet of agents running constant heartbeats can cost hundreds of thousands annually just to maintain status checks. Vendor lock-in now happens not just at the API level but through accumulated context, workflows, and integrations tuned to a specific provider’s models. Switching costs are no longer just about code migration—they’re about losing months of institutional memory embedded in your agents.
Over the next year, I’m watching four key signals. First, whether OpenClaw’s defaults shift from Claude to OpenAI models, signaling revenue redirection. Second, if Steinberger’s projects at OpenAI mirror OpenClaw’s agent approach but built on OpenAI’s stack. Third, Anthropic’s response—will they partner with or acquire another agent platform to reclaim distribution? And fourth, whether agent platform defaults become a negotiation point in enterprise API contracts, akin to search engine default deals.
Ask yourself: do you know where your API spend is going? Have you updated your budgets for the explosive token burn of autonomous agents or are you still thinking in chatbot terms? Would you notice if your agent platform’s default model changed tomorrow? The headlines have moved on from the acqui-hire narrative, but the token economics haven’t. Understanding who controls your agent defaults is no longer just a technical choice—it’s a financial one.
You can read the full article—with all the data and sources—on ThePragmaticCTO Substack.
Read the full article — with all the data and sources — on ThePragmaticCTO.
