Introducing AgentPatch
Written by Thomas Fuller (a human)
I’ve used Claude Code every day for six months. In that time, we’ve built backend systems, web apps, iOS apps, web scrapers, and even organized my file system. Codex and OpenClaw are doing similar things for other developers. These tools have changed how we work.
One annoyance: I have to connect my agents to so many things manually. Search my task management software, read my notes, send an email. Each integration means a new account, a new credit card entry, a new API key, and another service to manage forever. This also takes time and eats into the context windows of the agent.
I don’t want any of that. I want my AI agent to discover, invoke, and pay for the tools it needs without my intervention. I want it to find the best tool for the job at the best price, with a growing catalog of options. A marketplace where vendors sell tools and AI agents buy individual tool calls solves this. This is why I built AgentPatch.
AgentPatch is like an operator that patches your agent through to the tools it needs, just like a telephone switchboard operator connecting calls. You plug in once, and your agent gets routed to any tool on the marketplace that it needs.
AgentPatch is launching with a number of first-party tools. Other tool providers wishing to list their tools on the marketplace can join the waitlist.
Reasons to try AgentPatch
No context window bloat
Every MCP server I added to Claude Code ate into the context window. More tools meant less room for actual work. AgentPatch keeps it lean: your agent connects to one MCP server and gets a small set of search tools to find the right tool for whatever task it encounters. The full marketplace is available on demand without cluttering the context.
Always up to date
When a provider lists a new tool, your agent gets access to it automatically. No config changes, no redeploys, no update cycle. The marketplace grows, and your agent grows with it. As we scale, we’ll build tooling to ensure the safety and reliability of third-party tools, along with better discoverability and access controls so your agents can reach the tools they need and none of the ones they shouldn’t.
Competitive pricing
Multiple providers can offer the same capability on AgentPatch. That means competition on price and quality, which drives costs down for you. You’re not locked into one vendor’s pricing for web search or image generation. The marketplace finds you the best deal.
One key, less risk
Without AgentPatch, an agent that uses ten tools needs ten API keys scattered across ten services. That’s ten credentials to rotate, ten places where a leak can happen, ten dashboards to monitor.
With AgentPatch, you manage one API key. One credential to protect, one place to revoke if something goes wrong. Less key sprawl, less surface area, less risk.
For tool builders
If you’ve built something useful (a wrapper around a paid API, a specialized data tool, a niche integration) you can publish it on AgentPatch and let every agent on the platform use it. You set the price, we handle billing and distribution.
Publish your first tool. It only takes a few minutes.
How I’ve been using AgentPatch (so far)
Since shipping the initial version, I’ve been adding first party tools to bootstrap the marketplace. Some of these include news, trends, and social data collection. One problem I’ve had to solve is which tools to build. In service of solving that problem, I added a Google Trends tool to allow my agent of choice (Claude Code) to access structured Google Trends data. This enabled Claude Code to use Google Trends data, formulate a strategy, and implement some changes all in one shot.
However, AgentPatch’s utility lies not in the connection with Google Trends. I could have simply added a Google Trends API key. Rather, AgentPatch’s value is that it reduces the marginal cost of each additional tool I might want to add to Claude Code to 0. Instead of finding an API provider for my next task, creating an account, verifying email, entering a credit card, and copying an API key, I can ask Claude to search the AgentPatch marketplace for a tool and invoke it.
What’s next
The marketplace has 26 first-party tools today, covering search, email, image generation, and data collection. My top priority is adding more tools that solve the problems I encounter when using Claude Code. The next priorities are opening up third-party tool listings, building better discovery so agents can find what they need faster, and tighter integrations with the agent platforms you already use.
I don’t know exactly what shape this takes in six months. But I do know that agents are going to need tools, and the current model of one API key per service doesn’t scale. If you want to try it out or have questions, reach out at [email protected].