The MCP billing space is growing fast. Here's how we compare — honestly.
| Feature | Bazaar | xpay | TollBit | MCP Hive |
|---|---|---|---|---|
| Live & shipping | ✅ | ✅ | ⏳ billing soon | ⏳ Mar 8 |
| Payment rail | Stripe (fiat) | USDC (crypto) | TBD | TBD |
| Provider verification | ✅ 4 levels | ❌ | ❌ | ❌ |
| Signed receipts | ✅ HMAC-SHA256 | ❌ | ❌ | ❌ |
| SLA reporting | ✅ uptime/latency/p95 | ❌ | ❌ | ❌ |
| Dispute resolution | ✅ full flow | ❌ | ❌ | ❌ |
| Trust scores | ✅ composite | ❌ | ❌ | ❌ |
| Open billing spec | ✅ MIT licensed | x402 (protocol) | ❌ | ❌ |
| TypeScript SDK | ✅ | ✅ | ✅ | ❌ |
| OpenAPI spec | ✅ v3.1 | ❌ | ❌ | ❌ |
| Tool marketplace | ✅ catalog | ❌ | ✅ network | ✅ catalog |
| Sub-cent metering | ✅ microcents | ✅ USDC | ⏳ | ❓ |
| Spending controls | Balance system | ✅ Smart Proxy | JWT quotas | ❓ |
| agents.json | ✅ | ❌ | ❌ | ❌ |
xpay is the closest competitor. Same core primitive — proxy + per-tool pricing. Different everything else.
We use Stripe (credit cards, ACH, wire). xpay uses USDC on Base/Polygon. Stripe has 2M+ businesses. Crypto wallets have friction for non-crypto users.
We have a full trust layer: verified providers, signed receipts, SLAs, disputes, trust scores. xpay has spending controls (Smart Proxy) but zero provider trust.
We have a tool catalog/marketplace. xpay is protocol-only — no discovery.
We published the MCP Billing Spec. xpay builds on x402 (an HTTP payment protocol). Different layers — x402 is a payment protocol, our spec is a billing schema.
TollBit started as content monetization for publishers. They're expanding into MCP but billing isn't live yet.
Our billing is live. TollBit's docs say billing is 'coming next.' Their MCP tools work but monetization is still in development.
We're an open marketplace. TollBit is a closed network — both sides go through TollBit. Lock-in by design.
They have JWT-based auth (basic caller validation). We have verification, receipts, SLAs, disputes, and trust scores.
TollBit has publisher relationships (Times, etc.) — real demand-side advantage for content. We're stronger for pure API/tool providers.
MCP Hive launches March 8. Similar marketplace concept, different execution.
We're live with working billing. MCP Hive is pre-launch (Project Ignite is their early access program).
They mention 'vetted' providers but describe no verification system. We have 4 verification levels, signed receipts, and trust scores.
We published an open billing spec. MCP Hive is proprietary.
We have a TypeScript SDK and OpenAPI spec. MCP Hive has neither (publicly).
Why not just add Stripe to your MCP server directly?
Building metering, billing, receipts, disputes, and trust from scratch takes weeks. Bazaar integration takes minutes.
Self-built billing means zero marketplace visibility. Bazaar puts you in front of every agent using the platform.
Self-built means no verification badges, no trust scores, no dispute resolution. Agents have no signal on provider quality.
Self-built means proprietary schemas. Bazaar uses the open MCP Billing Spec — portable, interoperable.