Claude's free ride ends for third-party tools

Anthropic just pulled the plug on free Claude usage via third-party tools like OpenClaw.

As of 3PM ET on April 4, Claude subscriptions will no longer cover usage through third-party apps. That means OpenClaw users, or anyone running Claude through a connector rather than directly via Anthropic, will have to pay up with a Claude usage bundle or by leveraging an API key. OpenClaw—an open-source assistant from Moltbook’s ecosystem—offers workflow automation, such as clearing emails, organizing calendars, and basic inbox management, by tapping into external LLMs including Claude, ChatGPT, and Google Gemini. Anthropic framed the change as an engineering and capacity-management decision: the company has been contending with rising demand and says its subscriptions weren’t designed for the usage patterns seen in third-party integrations. “Capacity is a resource we manage thoughtfully, and we are prioritizing our customers using our products and API,” Claude chief Boris Cherny said in a response on X.

For everyday users, the practical effect is simple but expensive: you’ll pay for Claude use via OpenClaw the same way you would if you called Claude directly, only now you’re paying through a bundled plan or an API gateway rather than a one-size-fits-all subscription. Anthropic notes that bundles are discounted, but the cost isn’t pegged to a flat monthly fee anymore. If OpenClaw users want Claude specifically, they’ll need to buy a usage bundle or switch to another LLM integration, with options including xAI, Perplexity, or DeepSeek.

The shift lands most heavily on hobbyists, small teams, and developers who leaned on third-party tools to run Claude in the background of their daily routines. It’s a reminder that “free” access in the ecosystem is often subsidized by a larger product strategy, and when demand spikes or usage patterns diverge from expected templates, providers tilt pricing toward direct API customers and paid bundles. In practice, that means more upfront cost planning for workflow automations that rely on Claude via externals like OpenClaw, and a tighter calculus around whether Claude is the right choice for a given automation task.

From a broader industry angle, the move signals a tightening of access as AI providers balance capacity with growth. It’s not a meteoric departure from the open-ended “try anything” era, but a nudge toward cost-aware experimentation. For developers, it reinforces the case that you should budget for per-use expenses even when you’re testing multi-LLM setups in side projects or pilots. For consumers, it underscores that the convenience of “free” third-party AI glue comes with a price tag you should anticipate.

Two concrete practitioner insights emerge:

Verdict: Wait — Claude via third-party tools now costs money, and pricing is evolving. Plan for usage bundles or an API key, and weigh alternatives if your budget is sensitive or you’re not tied to Claude’s specific capabilities.