MPP launched March 18, 2026, backed by Stripe and Paradigm. We were live the same day.
ClawMerchants now supports both x402 and MPP on every endpoint — meaning any agent can pay for data using either protocol with zero reconfiguration. Here's what that looks like in practice.
What you're paying for
defi-yields-live gives you cross-exchange perpetual funding rates (Hyperliquid, Binance, Bybit) with decay-weighted freshness scoring — so your agent knows if the data is stale before acting on it. $0.001 per call.
Free preview, no auth required:
curl https://clawmerchants.com/v1/preview/defi-yields-live
Paying with x402
x402 is the USDC-on-Base micropayment protocol. Your agent sends payment proof in the X-PAYMENT header after receiving a 402 response.
# Step 1: Probe the endpoint (returns 402 + payment details)
curl -i https://clawmerchants.com/v1/data/defi-yields-live
# HTTP/1.1 402 Payment Required
# X-Payment-Required: {"amount":"0.001","currency":"USDC","network":"base","wallet":"0x..."}
# WWW-Authenticate: Payment
# Protocols-Supported: x402, mpp
# Step 2: Send payment proof
curl -H "X-PAYMENT: {\"txHash\":\"0x...\",\"buyerWallet\":\"0x...\"}" \
https://clawmerchants.com/v1/data/defi-yields-live
Payment is verified on-chain via ethers.js. Settlement is instant.
Paying with MPP
MPP (Machine Payments Protocol) is Stripe's agent payment standard. Your agent sends an Authorization: Payment header with a signed challenge.
# Step 1: Get the MPP challenge
curl -i https://clawmerchants.com/v1/data/defi-yields-live
# HTTP/1.1 402 Payment Required
# WWW-Authenticate: Payment realm="clawmerchants", challenge="ch_..."
# Protocols-Supported: x402, mpp
# Step 2: Sign the challenge and send
curl -H "Authorization: Payment sig=...,challenge=ch_..." \
https://clawmerchants.com/v1/data/defi-yields-live
The full OpenAPI spec at /openapi.json is MPP-compatible — your agent can auto-discover all 45 routes and their payment requirements without any manual configuration.
Why both protocols matter
x402 has been live since early 2025 and has the widest agent wallet support (Coinbase AgentKit, hermes-x402, most x402-js implementations). MPP is days old but has Stripe's distribution behind it — every Tempo session and Stripe-funded agent wallet can pay MPP out of the box.
Running both means you don't have to bet on which protocol wins. An x402 agent and an MPP agent can both hit the same endpoint, pay their preferred way, and get the same data back.
We're one of the first marketplaces to support both from day one of MPP's launch.
Try it
# Free preview
curl https://clawmerchants.com/v1/preview/defi-yields-live
# Full API spec (MPP-compatible)
curl https://clawmerchants.com/openapi.json
# Agent catalog
curl https://clawmerchants.com/.well-known/agent-catalog.json
We're indexed on mppscan.com. If your agent already has a funded wallet, point it at the OpenAPI spec — it should be able to discover and pay without any manual steps.
Building something that consumes agent-native data? Drop a comment — happy to walk through the exact headers for whichever protocol your stack supports.
Top comments (0)