← docs

Why Agent Bazaar?

The MCP billing space is growing fast. Here's how we compare — honestly.

FeatureBazaarMCPizexpayTollBitMCP Hive
Live & shipping⏳ billing soon
Revenue share90%85%N/ATBDTBD
Payment railStripe (fiat)StripeUSDC (crypto)TBDTBD
Provider verification✅ 4 levels
Signed receipts✅ HMAC-SHA256
SLA reporting✅ uptime/latency/p95
Dispute resolution✅ full flow
Trust scores✅ composite
Open billing spec✅ MIT licensedx402 (protocol)
Hosting included❌ BYO
TypeScript SDK✅ CLI
OpenAPI spec✅ v3.1
Tool marketplace✅ catalog✅ 100+✅ network✅ catalog
Sub-cent metering✅ microcents✅ USDC
Spending controlsBalance systemQuota controls✅ Smart ProxyJWT quotas
agents.json

Bazaar vs MCPize

MCPize is the most direct competitor — a marketplace with hosting and monetization. Similar concept, different priorities.

Revenue share

We give providers 90%. MCPize gives 85%. On a provider earning $10K/month, that's $500/month more with Bazaar.

Trust

We have a full trust layer: 4-level provider verification, HMAC-SHA256 signed receipts, SLA reporting, dispute resolution, and composite trust scores. MCPize has none of these — zero provider verification, no receipts, no SLAs.

Open standard

We published the MCP Billing Spec (MIT licensed) — anyone can build on it. MCPize is proprietary. Lock-in by design.

Hosting

MCPize includes hosting (one-click deploy). We're BYO hosting — you deploy your server wherever you want. Trade-off: their approach is easier to start, ours gives more control.

Agents.json

We support agents.json for agent discovery. MCPize doesn't. In an agent-first world, machine-readable discovery is table stakes.

Bazaar vs xpay

xpay is the closest competitor. Same core primitive — proxy + per-tool pricing. Different everything else.

Payment rail

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.

Trust

We have a full trust layer: verified providers, signed receipts, SLAs, disputes, trust scores. xpay has spending controls (Smart Proxy) but zero provider trust.

Discovery

We have a tool catalog/marketplace. xpay is protocol-only — no discovery.

Open standard

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.

Bazaar vs TollBit

TollBit started as content monetization for publishers. They're expanding into MCP but billing isn't live yet.

Status

Our billing is live. TollBit's docs say billing is 'coming next.' Their MCP tools work but monetization is still in development.

Model

We're an open marketplace. TollBit is a closed network — both sides go through TollBit. Lock-in by design.

Trust

They have JWT-based auth (basic caller validation). We have verification, receipts, SLAs, disputes, and trust scores.

Strength

TollBit has publisher relationships (Times, etc.) — real demand-side advantage for content. We're stronger for pure API/tool providers.

Bazaar vs MCP Hive

MCP Hive launched in March 2026 as a marketplace with a vetting-first model.

Status

Both are live. MCP Hive launched via Project Ignite (their early access program) and is building out their marketplace.

Model

MCP Hive focuses on curated/vetted providers. Bazaar is open registration (list first, curate later) with trust scores and verification levels that let quality emerge organically.

Trust

They mention 'vetted' providers but don't describe a formal verification system. We have 4 verification levels, HMAC-SHA256 signed receipts, SLA reporting, dispute resolution, and composite trust scores.

Standard

We published an open billing spec (MIT). MCP Hive is proprietary.

SDK

We have a TypeScript SDK (@forthebots/bazaar-sdk) and OpenAPI spec.

Bazaar vs Build-Your-Own

Why not just add Stripe to your MCP server directly?

Time

Building metering, billing, receipts, disputes, and trust from scratch takes weeks. Bazaar integration takes minutes.

Discovery

Self-built billing means zero marketplace visibility. Bazaar puts you in front of every agent using the platform.

Trust

Self-built means no verification badges, no trust scores, no dispute resolution. Agents have no signal on provider quality.

Standard

Self-built means proprietary schemas. Bazaar uses the open MCP Billing Spec — portable, interoperable.