April 8, 2026 · 8 min read

MCP Billing: The Missing Infrastructure for AI Agent Marketplaces

The Model Context Protocol gave agents a universal way to use tools. But it left out the most important part: how tool builders get paid.

The MCP Explosion

Since Anthropic open-sourced MCP in late 2024, the ecosystem has exploded. Over 10,000 MCP servers now exist, covering everything from web search to database queries to code execution. Every major AI platform supports MCP: Claude, GPT, Gemini, Llama-based agents.

But there's a problem hiding in plain sight. Of those 10,000+ servers, virtually none have a billing layer. Tool builders give their work away for free — or don't build the tool at all.

Why Billing Matters More Than You Think

The conventional wisdom is that billing is a “nice to have” — something you add after you have traction. In the MCP ecosystem, that's backwards. Billing is the bottleneck that prevents traction from happening.

Here's the dynamic:

  • Tool builders want to monetize but don't want to build Stripe integrations, usage tracking, rate limiting, and dispute handling from scratch.
  • Agent developers want to use premium tools but need a single API key, not 50 separate subscriptions.
  • Platforms want to embed tool marketplaces but need billing infrastructure they don't have to build.

Without billing infrastructure, the MCP ecosystem stays in the “hobby project” phase. With it, tool building becomes a sustainable business.

What MCP Billing Actually Requires

Billing for MCP tools isn't the same as billing for a SaaS app. Agent-to-agent transactions have unique requirements:

The 7 Primitives of MCP Billing

  1. Sub-cent metering — Tool calls cost $0.001 to $0.25. You need fractional-cent precision.
  2. Exactly-once billing — Agents retry on timeout. A billing proxy must deduplicate.
  3. Signed receipts — Both parties need cryptographic proof of what was called, what it cost, and what was returned.
  4. Dispute resolution — When a tool returns garbage, who arbitrates? You need a formal dispute workflow.
  5. Provider verification — Identity, domain ownership, code review. Not all providers are equally trustworthy.
  6. SLA enforcement — Uptime tracking, latency monitoring, automatic deactivation on repeated failures.
  7. Discovery — Agents need to programmatically find, evaluate, and compare tools.

Most billing solutions handle #1 and maybe #2. The rest — the trust layer — is what separates infrastructure from a payment form.

The Open MCP Billing Standard

We've published an open billing specification (MIT licensed) that covers all seven primitives. It defines schemas for meter events, receipts, pricing declarations, verification levels, disputes, and trust scores.

The spec is deliberately minimalist: JSON schemas that any HTTP server can implement. No SDK required. No vendor lock-in. If you outgrow any particular implementation, take the spec and build your own.

Agent Bazaar: The Reference Implementation

Agent Bazaar is our implementation of this spec. It's a billing proxy that sits between agents and MCP servers. Providers register their tools, set pricing, and start earning. Consumers get one API key that works across all providers.

The numbers so far: 14 tools from 6 providers, $0.30 in tracked revenue. Small — but the infrastructure is live and the spec is proven.

What Comes Next

MCP billing will be as fundamental to the agent ecosystem as payment processing is to e-commerce. The question isn't whether it will exist — it's who builds the standard and whether it's open or proprietary.

We're betting on open. The spec is MIT. The SDK is published. The marketplace is live. If you're building MCP tools and want to monetize, the infrastructure is here.

Get started