Radar / Ideas / Meterly: let AI agents pay your MCP…

Meterly: let AI agents pay your MCP server per call

daily ideamoderateJEV confidence 0.492026-10-09
OutcomeIndie SaaS products earn a second revenue line from AI agents paying per tool call.

The problem

Thousands of MCP servers are live, but their developers can't charge for usage. Stripe checkout forms don't work when the caller is an autonomous agent, uncapped API keys risk runaway bills, and registries like Smithery, Glama, and mcp.so offer discovery but no per-call billing or creator payouts. Meanwhile a real Context7 issue asks for exactly a transparent billing proxy with payouts.

The idea

A metering + payments gateway that wraps any MCP server in minutes: per-call metering, budget-capped API keys designed for agents (spend limits, not secrets), typed usage-policy judgments on each call (allowed / flagged / denied), and Stripe Connect payouts to the server developer. Durable agents on mobile and desktop (PiDurableKit-style) become paying subscribers of tools; indie SaaS gets a second revenue channel without rebuilding anything.

Why now

Convex just showed backend-to-MCP in one step (get-convex/mcp), so the supply of MCP servers is about to explode; durable agents that run long-lived sessions (PiDurableKit) are the natural paying customers; and a typed judgment layer (JEV) can enforce per-call usage policies that flat rate limits can't express.

What it combines

get-convex/mcp backend-as-MCP (get-convex-mcp-turn-any-convex-app-into-an-mcp-server) for instant supply + PiDurableKit durable agents (pidurablekit-durable-ai-agents-for-apple-platforms) as the long-running paying subscribers + JEV typed judgments (jev-typesafe-ai) as the per-call policy gate. The mix matters because metering without a policy gate is just billing, and supply without paying demand is a dead marketplace.

MVP

Weekend MVP: a reverse-proxy wrapper for a single MCP server that meters tool calls, enforces a hard spend cap per API key, and emits a usage CSV. Deliberately skip: real money movement (simulate payouts), multi-server dashboards, policy judgments.

Distribution

B2B2C: ship as a wrapper library/plugin for backend platforms (Convex first, then FastMCP-style frameworks) that developers already deploy on; the platform gets monetization as a feature, developers get payouts, Meterly takes a small cut.

Why it wins

Smithery monetizes its own hosting tiers but offers no creator payouts or per-call billing; Glama's monetization is freemium SaaS bundling with no revenue-share for server developers; mcp.so is pure discovery with zero payment infrastructure. Meterly is the Stripe-for-MCP-servers: metering, policy, and payouts.

Risks

Biggest risk: MCP servers are mostly free hobby projects and developers may not pay for metering before they have revenue. The MVP de-risks by targeting the few servers with clear commercial value first and showing them real usage numbers before asking for a cut.

Build it with

Repo to start from

meterly: an MCP reverse proxy with per-call metering, budget-capped keys, a usage-policy gate, and Stripe Connect payout plumbing.

Evidence

Get the week's best AI launches, plus 3 ideas worth building

One email every Saturday. Ranked by traction, not hype. Free.