{"artifact":{"apiPath":"/api/reports/mpp-vs-x402-for-production-buyers-2026/evidence","byteLength":6607,"description":"Structured evidence ledger tying claims and charts back to cited sources.","format":"evidence","label":"Evidence artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"9dd405d79396b576625d10e852c999ce8bf7e810417ada590d227c7988c16464","status":"live"},"document":{"chartProvenance":[{"chartTitle":"Which payment model should dominate each buyer use case","sourceLabels":["Tempo Mainnet launch","Welcome to x402","Stripe machine payments","Alchemy x402 vs MPP"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.cdp.coinbase.com/x402/welcome","https://docs.stripe.com/payments/machine","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"whyUseful":"Shows buyers where the stack boundary should actually sit for request-priced calls, recurring sessions, and production billing recovery."},{"chartTitle":"Where retry, renewal, and refill logic actually belongs","sourceLabels":["Stripe machine payments","Circle USDC","Crossmint protocols compared"],"sourceUrls":["https://docs.stripe.com/payments/machine","https://www.circle.com/usdc","https://www.crossmint.com/learn/agentic-payments-protocols-compared"],"whyUseful":"Separates the first charge from the recurring recovery loop so buyers do not confuse protocol capability with billing ownership."}],"claims":[{"chartTitles":["Which payment model should dominate each buyer use case"],"confidence":"high","id":"request-boundary-is-the-real-x402-case","kind":"comparison","section":"The request boundary is the real x402 use case","sourceLabels":["Welcome to x402","Stripe machine payments","Alchemy x402 vs MPP"],"sourceUrls":["https://docs.cdp.coinbase.com/x402/welcome","https://docs.stripe.com/payments/machine","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"statement":"x402 is strongest when the merchant can charge each request independently and does not need a longer-lived recurring payment envelope between calls."},{"chartTitles":["Which payment model should dominate each buyer use case","Where retry, renewal, and refill logic actually belongs"],"confidence":"high","id":"sessions-change-the-problem","kind":"finding","section":"Session rails matter when continuity is the product","sourceLabels":["Tempo Mainnet launch","Stripe machine payments","Crossmint protocols compared"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.stripe.com/payments/machine","https://www.crossmint.com/learn/agentic-payments-protocols-compared"],"statement":"MPP or another session rail becomes more useful when the system must preserve paid continuity across repeated autonomous runs rather than merely repeat one-shot charges."},{"chartTitles":["Which payment model should dominate each buyer use case","Where retry, renewal, and refill logic actually belongs"],"confidence":"high","id":"renewal-is-not-just-another-charge","kind":"comparison","section":"Renewal and refill belong above the first charge","sourceLabels":["Stripe machine payments","Circle USDC","Crossmint protocols compared"],"sourceUrls":["https://docs.stripe.com/payments/machine","https://www.circle.com/usdc","https://www.crossmint.com/learn/agentic-payments-protocols-compared"],"statement":"Recurring renewal and refill are operational billing questions because they extend what the system may keep doing later, so merchant billing and treasury controls should dominate more than the protocol edge."},{"chartTitles":["Where retry, renewal, and refill logic actually belongs"],"confidence":"high","id":"customer-recovery-lives-in-billing","kind":"finding","section":"Customer recovery lives in billing and treasury","sourceLabels":["Stripe machine payments","Circle USDC","Alchemy x402 vs MPP"],"sourceUrls":["https://docs.stripe.com/payments/machine","https://www.circle.com/usdc","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"statement":"Failed customer subscriptions, grace periods, retries, and recovery messaging usually belong in merchant billing and treasury operations instead of the raw payment protocol layer."},{"chartTitles":["Which payment model should dominate each buyer use case"],"confidence":"high","id":"buyers-should-choose-by-rollout-order","kind":"comparison","section":"Rollout order matters more than protocol branding","sourceLabels":["Tempo Mainnet launch","Welcome to x402","Alchemy x402 vs MPP"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://docs.cdp.coinbase.com/x402/welcome","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"statement":"Production buyers should choose by rollout order: stay request-priced first, add sessions when continuity matters, and add billing or treasury layers when recurring recovery becomes part of the product."},{"chartTitles":["Where retry, renewal, and refill logic actually belongs"],"confidence":"high","id":"merchant-layer-still-matters","kind":"finding","section":"Bottom line","sourceLabels":["Stripe machine payments","Circle USDC","Crossmint protocols compared"],"sourceUrls":["https://docs.stripe.com/payments/machine","https://www.circle.com/usdc","https://www.crossmint.com/learn/agentic-payments-protocols-compared"],"statement":"Neither x402 nor MPP replaces merchant billing, refill, reconciliation, and treasury visibility once the product sells recurring agent work to real customers."}],"generatedAt":"2026-03-24T00:00:00.000Z","slug":"mpp-vs-x402-for-production-buyers-2026","summary":{"chartBackedClaimCount":4,"claimCount":6,"ecosystemSourceCount":2,"officialSourceCount":4,"totalSourceCount":6},"title":"MPP vs x402 for Production Buyers, 2026"},"generatedAt":"2026-05-04T00:18:27.443Z","kind":"deep_report_evidence","operatorAccess":null,"payer":null}