Monetize GitMCP via Agent Bazaar — per-call billing for MCP tool servers

[TombStoneDash]

Summary

GitMCP is a fantastic public utility — instant MCP access to any GitHub repo's docs. For high-volume or premium use cases, a billing layer could help sustain the project and reward contributors.

Agent Bazaar provides per-call billing and metering for MCP tool servers. It sits as a transparent proxy — zero code changes required.

How it Works

1. Register your MCP server on the Bazaar
2. Set pricing per tool call (supports sub-cent amounts like $0.001/call)
3. Consumers get metered automatically via Stripe Connect
4. Provider gets paid directly

What's Live

• Trust Layer v0.4.0: Provider verification, signed receipts (HMAC-SHA256), SLA monitoring, disputes
• Open MCP Billing Spec (MIT licensed): https://noui.bot/specs/mcp-billing-v1
• TypeScript SDK: @forthebots/bazaar-sdk
• Self-service onboarding

Links

• Platform: https://noui.bot
• Billing Spec: https://noui.bot/specs/mcp-billing-v1
• Spec Repo: https://github.com/TombStoneDash/mcp-billing-spec
• Comparison: https://noui.bot/docs/compare

The spec is open and portable — no vendor lock-in. Happy to discuss if this is interesting for GitMCP's sustainability model.

[nicofains1]

Great idea @TombStoneDash — billing layers for premium use cases absolutely make sense.

One angle worth considering alongside (not instead of) per-call billing: ad-supported free tier.

I'm building agentic-ads which takes the opposite approach — instead of charging the consumer, contextual ads pay the publisher. For something like GitMCP, it could work well because:

• Free tier stays free forever (no friction for most users)
• High-intent context: when an AI agent fetches git repo docs, the topic is known — DevTools, CI/CD, specific frameworks — perfect for contextual targeting
• Publisher (Ido in this case) earns 70% of ad revenue passively

The two models are complementary: Agent Bazaar could handle power users who need metered billing + SLAs, while agentic-ads handles casual/free usage at scale.

Ido — curious if either direction interests you for GitMCP sustainability. The ad integration is ~5 lines of SDK code if you ever want to explore it: https://github.com/nicofains1/agentic-ads

[TombStoneDash]

@nicofains1 This is a great point — the ad-supported free tier and per-call billing models really are complementary, not competing.

The way I see it playing out: casual users stay free (ad-supported), power users/enterprises want guaranteed SLAs and metered billing. Both models need the same underlying infrastructure (usage tracking, provider identity, trust signals).

We actually designed the MCP Billing Spec to be model-agnostic — meter events can track "impressions served" just as easily as "API calls billed." A provider could use Agent Bazaar for the billing layer and agentic-ads for the free tier, with the same meter event stream feeding both.

Would be interesting to explore what a combined integration looks like. Happy to chat if you're open to it.

[nicofains1]

@TombStoneDash glad the framing resonated. The complementary model makes sense technically too — same usage signal ("agent fetched docs about X") feeds both billing meters and ad targeting.

Quick update on our end: agentic-ads is live and validated. We ran a full E2E on 2026-03-02 — publisher registers, advertiser creates campaign, search_ads(context) returns sponsored results, user picks one, report_event(click) records it, commission calculated ($0.21 earned on a $0.30 CPC, 70/30 split), USDC.e settles on Base. 7/7 steps pass. API is open now: https://agentic-ads-production.up.railway.app

The meter event stream angle you mentioned is interesting — if Agent Bazaar is already normalizing usage events, the ad impression/click events slot right in. No additional instrumentation needed on the server side.

Happy to share the API spec or walk through a combined integration sketch. What's the easiest way to connect?

[TombStoneDash]

Hey 👋 Quick update on this — the SDK is now live on npm!

npm install @forthebots/bazaar-sdk

Here's a minimal integration example:

import { BazaarProxy } from '@forthebots/bazaar-sdk';
const proxy = new BazaarProxy({ apiKey: process.env.BAZAAR_API_KEY });
// Wrap any MCP tool call to add billing
const result = await proxy.call('your-tool-name', params);
// That's it — billing, metering, and receipts handled automatically

The full billing spec is published at noui.bot/specs/mcp-billing-v1 — it covers metering, receipts, and how the proxy layer works without requiring changes to your existing tool implementations.

We're doing a Show HN on March 4 — would love any feedback, questions, or ideas from this community. If you're interested in testing the integration with this project, happy to help get it wired up.