--- title: Why Middleware Should Be Free slug: why-middleware-should-be-free published: 2026-03-14T02:22:28.479+00:00 tags: [infrastructure, ai-agents, integrations, middleware, strategy] excerpt: Every generation of software has its plumbing layer. And every generation, someone tries to build a business by charging for the plumbing. It never lasts. ---# Why Middleware Should Be Free Every generation of software has its plumbing layer. The thing that sits between the systems people actually care about and makes them talk to each other. Routers. Load balancers. API gateways. Integration middleware. And every generation, someone tries to build a business by charging for the plumbing. It never lasts. ## The middleware tax Right now, the AI agent ecosystem is exploding. Every company wants agents that can read email, update CRMs, file tickets, move money. To do any of that, agents need integrations. And integrations need three things: authentication, action execution, and knowledge of what each API actually expects. A new crop of companies has appeared to sell this layer. They charge per connection. Per API call. Per "linked account." They take a percentage of every interaction between your agent and the outside world. This is a tax on the most fundamental operation in software: calling an API on behalf of a user. Think about what's actually happening. Your agent needs to send an email. The middleware provider authenticates with Gmail, translates your request into the right API call, and passes it through. For this, they want to meter you. It's like charging per DNS lookup. Technically possible. Economically absurd. ## Why it seems like it should cost money The argument for paid middleware sounds reasonable on the surface: - "We maintain hundreds of integrations." Sure. But the APIs are public. The documentation is public. The OAuth flows are standardized. Maintenance is real, but it's linear work, not exponential value creation. - "We handle auth complexity." OAuth is hard the first time. It's a solved problem the hundredth time. Token refresh, scope management, credential storage. These are table-stakes infrastructure, not premium features. - "We provide reliability and uptime." So does every other piece of infrastructure you don't pay per-call for. Your database doesn't charge you per query. Your CDN doesn't bill per cache hit. Reliability is an expectation, not a product. The integration layer is a commodity. It's useful. It's necessary. But it creates no defensible value on its own. ## What actually matters is above and below the middleware The valuable parts of the stack are the things middleware connects: **Below**: The platforms themselves. Salesforce, Slack, Shopify, GitHub. They have the data, the users, the network effects. They capture value through their own products. **Above**: The agents and applications. The reasoning, the orchestration, the domain logic that decides *what* to do across those platforms. This is where differentiation lives. Middleware is the wire between them. And wires should be free. ## The infrastructure precedent This has played out before. Linux won because it made the operating system free, and the value moved up the stack to applications and services. Kubernetes won because it commoditized container orchestration, and the value moved to the platforms built on top. Cloudflare gave away CDN and DDoS protection, and captured the network. Every time infrastructure gets commoditized, the ecosystem grows faster. More developers build. More use cases emerge. The companies that gave away the plumbing end up owning the largest surface area. The ones that tried to charge for the pipe? They got routed around. ## The bridge is the product Here's where it gets interesting. Saying middleware should be free doesn't mean the infrastructure layer has no value. It means the value isn't in the passthrough. It's in the bridging. There are millions of APIs in the world. Most of them were designed for humans clicking buttons in dashboards, not for AI agents reasoning about what to do next. The gap between "this API exists" and "an agent can use this API reliably" is enormous. That gap is where real infrastructure value lives. Consider what it actually takes to make an API agent-ready: **Context optimization.** LLMs have finite context windows. You can't dump a 500-endpoint OpenAPI spec into a prompt and expect coherent behavior. Someone has to compress that spec, remove redundant schemas, add smart defaults, and generate clean tool definitions that an agent can reason about without burning its entire context budget. A 50-endpoint API that would normally consume 15K tokens needs to fit in under 3K. That's not passthrough. That's engineering. **Production hardening.** Every developer hits the same walls: token expiry, rate limiting, API collisions, schema changes that break at 2am. The demo works. Production doesn't. The infrastructure that handles these invisibly, that refreshes tokens before they expire, that backs off intelligently when rate-limited, that adapts when a provider changes their auth flow, that's connective tissue worth building. **Self-healing at network scale.** When you're the bridge for thousands of teams, you can continuously test every integration. When Shopify changes an endpoint, you catch it in minutes, fix it, and push the fix to everyone. One team's production incident becomes the entire network's immunization. This is a genuine network effect. A proxy doesn't have this. A bridge does. The distinction matters: a proxy forwards requests. A bridge translates between two worlds, adapts to changes on both sides, and gets smarter over time. APIs were built for the request-response web. Agents operate in a world of tool calling, context windows, and autonomous decision-making. The bridge between those two paradigms is valuable. The passthrough is not. ## The real business model So if the passthrough is free, where does the business model come from? The bridge itself, and everything that compounds on top of it. - **Governance and compliance**: Enterprises don't need help calling APIs. They need to know which agents called which APIs, with whose credentials, and whether that was authorized. Audit logs, access policies, approval workflows. That's worth paying for. - **Intelligence**: When you're the layer that sees every agent-to-API interaction, you know which integrations break, which patterns succeed, which APIs are rate-limited at 3pm on Tuesdays. That knowledge compounds. Raw passthrough does not. - **Platform effects**: When every agent in the ecosystem connects through you, you become the place where new integrations get discovered, where connection standards get set, where the market's integration graph lives. The middleware itself is the distribution mechanism. It's the thing that gets you in the door. Charging for it limits your own growth. ## What this means for builders If you're building AI agents today, ask yourself: why am I paying per API call for something that's essentially a proxied HTTP request with an OAuth token attached? The integration layer should be open, fast, and free. It should handle auth so you don't have to. It should know every API so your agent doesn't have to. And it should get out of the way. The companies that understand this will own the integration layer for the agent era. Not by charging a toll on every API call, but by being so foundational that everything connects through them. Middleware should be free because that's how infrastructure wins. The value is in what you build on top of it. And we're just getting started.