{"artifact":{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/bundle","byteLength":61537,"description":"Single purchase target returning the markdown report, JSON artifact, and manifest together.","format":"bundle","label":"Combined report bundle","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"d648ab723c9479c75c3acceec18bd34b6a7c73f5c3000c5030d4236b84ec6c5d","status":"live"},"bundle":{"charts":{"artifact":{"byteLength":2761,"fileName":"charts.json","format":"charts","mimeType":"application/json; charset=utf-8","sha256":"d2e96e9d16f2b02d5eb43f8f687a52f9d9861e60a383eadc26d487855ab0dcba"},"document":{"charts":[{"caption":"The strongest factual proof that x402 became more than a whitepaper is usage: public reporting on x402scan showed daily transactions jumping from roughly 1,000 to 300,000 in four days.","chartType":"area","points":[{"label":"2025-10-23","note":"[Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) summarized x402scan activity before the late-October surge at roughly one thousand daily transactions.","values":[1000]},{"label":"2025-10-24","note":"The same report marked October 24 as the first day the ecosystem crossed into six-figure daily transaction territory.","values":[100000]},{"label":"2025-10-25","note":"Activity roughly doubled again one day later, showing this was not a one-day spike.","values":[200000]},{"label":"2025-10-26","note":"By October 26, daily volume was reported around 300,000 transactions, making the production-usage case much harder to dismiss.","values":[300000]}],"series":["daily transactions"],"title":"x402 daily transaction surge in late October 2025","unit":"daily transactions"},{"caption":"The other useful question for buyers is not just whether x402 launched, but how much paid traffic and settled value accumulated after launch.","chartType":"bar","points":[{"label":"Oct 26, 2025 cumulative","note":"[Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) reported 1.446 million cumulative x402 transactions and about $1.59 million in settled volume after the first late-October burst.","values":[1446000]},{"label":"Nine months in market","note":"[O-mega.ai](https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026) cited roughly 140 million transactions and $43 million in settled volume within nine months.","values":[140000000]},{"label":"Coinbase public claim","note":"[DeFiPrime](https://defiprime.com/stripe-mpp-vs-x402) cited Coinbase's 50 million transaction claim for Agentic Wallets, which helps bracket how quickly paid agent traffic scaled.","values":[50000000]}],"series":["transactions"],"title":"x402 cumulative transaction milestones by March 2026","unit":"transactions"}],"generatedAt":"2026-03-22T00:00:00.000Z","slug":"tempo-x402-mcp-commerce-stack-2026-03"}},"definition":null,"evidence":{"artifact":{"byteLength":5379,"fileName":"evidence.json","format":"evidence","mimeType":"application/json; charset=utf-8","sha256":"9cc24ac778f24807f3b5408422ede9ab4cdb42b8bb57ebb34fd9e470a1b1d971"},"document":{"chartProvenance":[{"chartTitle":"x402 daily transaction surge in late October 2025","sourceLabels":["Panewslab x402 surge"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"],"whyUseful":"Turns the report's adoption argument into a measured usage curve instead of a conceptual protocol comparison."},{"chartTitle":"x402 cumulative transaction milestones by March 2026","sourceLabels":["Panewslab x402 surge","O-mega Tempo guide","DeFiPrime MPP vs x402"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09","https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026","https://defiprime.com/stripe-mpp-vs-x402"],"whyUseful":"Shows how quickly paid-agent traffic and settled value accumulated after launch, which matters more to buyers than launch timing alone."}],"claims":[{"chartTitles":[],"confidence":"high","id":"layer-boundary-mcp","kind":"finding","section":"Layer boundaries","sourceLabels":["MCP specification","x402 welcome"],"sourceUrls":["https://modelcontextprotocol.io/specification/2025-06-18","https://docs.cdp.coinbase.com/x402/welcome"],"statement":"MCP remains the tool and context transport layer and does not define native pricing or settlement."},{"chartTitles":[],"confidence":"high","id":"x402-http-handshake","kind":"finding","section":"Paid HTTP handshake","sourceLabels":["x402 welcome","MCP Server with x402"],"sourceUrls":["https://docs.cdp.coinbase.com/x402/welcome","https://docs.cdp.coinbase.com/x402/mcp-server"],"statement":"x402 standardizes the stateless HTTP 402 challenge-pay-retry loop that can sit beneath MCP tools and above a settlement network."},{"chartTitles":[],"confidence":"high","id":"mpp-session-operator-layer","kind":"comparison","section":"Settlement and sessions","sourceLabels":["Tempo Mainnet launch","Privy on Tempo MPP","Alchemy x402 vs MPP"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"statement":"Tempo Mainnet and MPP extend the stack with sessions, broader payment-method coverage, and operator-facing controls rather than replacing x402's negotiation layer."},{"chartTitles":[],"confidence":"medium","id":"composition-pattern-production","kind":"comparison","section":"Composition pattern","sourceLabels":["MCP Server with x402","Vercel x402-mcp","Tempo Mainnet launch"],"sourceUrls":["https://docs.cdp.coinbase.com/x402/mcp-server","https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools","https://tempo.xyz/blog/mainnet"],"statement":"The strongest production signal is composition: paid MCP tooling is already combining tool connectivity, paid HTTP, and settlement-oriented rails instead of collapsing them into one protocol."},{"chartTitles":["x402 daily transaction surge in late October 2025"],"confidence":"medium","id":"x402-daily-surge","kind":"chart","section":"Adoption and scale","sourceLabels":["Panewslab x402 surge"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"],"statement":"Public x402 volume reporting moved from roughly 1,000 daily transactions on October 23, 2025 to about 300,000 by October 26, turning the protocol from a spec story into a usage story."},{"chartTitles":["x402 cumulative transaction milestones by March 2026"],"confidence":"medium","id":"x402-cumulative-milestones","kind":"market","section":"Adoption and scale","sourceLabels":["Panewslab x402 surge","O-mega Tempo guide","DeFiPrime MPP vs x402"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09","https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026","https://defiprime.com/stripe-mpp-vs-x402"],"statement":"Cumulative public x402 activity reached 1.446 million transactions by late October 2025 and was cited in March 2026 reporting at roughly 140 million transactions after nine months in market."}],"generatedAt":"2026-03-22T00:00:00.000Z","slug":"tempo-x402-mcp-commerce-stack-2026-03","summary":{"chartBackedClaimCount":2,"claimCount":6,"ecosystemSourceCount":6,"officialSourceCount":5,"totalSourceCount":11},"title":"Tempo, x402, and the MCP Commerce Stack"}},"hashes":{"bundleSha256":"9696a20b8d30a3247d174cabb0fa8b83e52a8d611517587588024e4d28ba5063","chartsSha256":"d2e96e9d16f2b02d5eb43f8f687a52f9d9861e60a383eadc26d487855ab0dcba","definitionSha256":null,"evidenceSha256":"9cc24ac778f24807f3b5408422ede9ab4cdb42b8bb57ebb34fd9e470a1b1d971","jsonSha256":"1b43426048bb946b4ac1be41355f92a628293d23c6b282251a899b02d34b8ff9","markdownSha256":"40377a9ab5d71a003c6b92160b91f2e7c306773269015cf17a10364248a7c003","methodologySha256":"d2e0f3c9a2ddd5f2c24d778153be91f1b80c8d9251602df3045dc2b5895510a4","sourcesSha256":"f349d9670062576aa3cbfcd604602f8c3e2f6ec7a234c674e695cfdbdff36338"},"json":{"artifact":{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/json","byteLength":24181,"description":"Structured comparison matrix, source metadata, and stack-layer rows for downstream agents.","format":"json","label":"Full machine-readable JSON","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"1b43426048bb946b4ac1be41355f92a628293d23c6b282251a899b02d34b8ff9","status":"live"},"document":{"artifacts":[{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/markdown","byteLength":17342,"description":"Narrative positioning memo with stack diagrams, category boundaries, buyer guidance, and appendix notes.","format":"markdown","label":"Full markdown report","mimeType":"text/markdown; charset=utf-8","priceUsdc":0,"sha256":"40377a9ab5d71a003c6b92160b91f2e7c306773269015cf17a10364248a7c003","status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/json","byteLength":null,"description":"Structured comparison matrix, source metadata, and stack-layer rows for downstream agents.","format":"json","label":"Full machine-readable JSON","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":null,"status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/charts","byteLength":2761,"description":"Structured chart payload backing the inline report visuals and machine-readable consumers.","format":"charts","label":"Chart data artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"d2e96e9d16f2b02d5eb43f8f687a52f9d9861e60a383eadc26d487855ab0dcba","status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/sources","byteLength":2911,"description":"Structured source ledger with source kinds, labels, notes, and URLs.","format":"sources","label":"Sources artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"f349d9670062576aa3cbfcd604602f8c3e2f6ec7a234c674e695cfdbdff36338","status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/methodology","byteLength":1043,"description":"Structured methodology notes, dataset summary, and report timing metadata.","format":"methodology","label":"Methodology artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"d2e0f3c9a2ddd5f2c24d778153be91f1b80c8d9251602df3045dc2b5895510a4","status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/evidence","byteLength":5379,"description":"Structured evidence ledger tying claims and chart provenance back to cited sources.","format":"evidence","label":"Evidence artifact","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":"9cc24ac778f24807f3b5408422ede9ab4cdb42b8bb57ebb34fd9e470a1b1d971","status":"live"},{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/bundle","byteLength":null,"description":"Single purchase target returning the markdown report, JSON artifact, and manifest together.","format":"bundle","label":"Combined report bundle","mimeType":"application/json; charset=utf-8","priceUsdc":0,"sha256":null,"status":"live"}],"charts":[{"caption":"The strongest factual proof that x402 became more than a whitepaper is usage: public reporting on x402scan showed daily transactions jumping from roughly 1,000 to 300,000 in four days.","chartType":"area","points":[{"label":"2025-10-23","note":"[Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) summarized x402scan activity before the late-October surge at roughly one thousand daily transactions.","values":[1000]},{"label":"2025-10-24","note":"The same report marked October 24 as the first day the ecosystem crossed into six-figure daily transaction territory.","values":[100000]},{"label":"2025-10-25","note":"Activity roughly doubled again one day later, showing this was not a one-day spike.","values":[200000]},{"label":"2025-10-26","note":"By October 26, daily volume was reported around 300,000 transactions, making the production-usage case much harder to dismiss.","values":[300000]}],"series":["daily transactions"],"title":"x402 daily transaction surge in late October 2025","unit":"daily transactions"},{"caption":"The other useful question for buyers is not just whether x402 launched, but how much paid traffic and settled value accumulated after launch.","chartType":"bar","points":[{"label":"Oct 26, 2025 cumulative","note":"[Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) reported 1.446 million cumulative x402 transactions and about $1.59 million in settled volume after the first late-October burst.","values":[1446000]},{"label":"Nine months in market","note":"[O-mega.ai](https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026) cited roughly 140 million transactions and $43 million in settled volume within nine months.","values":[140000000]},{"label":"Coinbase public claim","note":"[DeFiPrime](https://defiprime.com/stripe-mpp-vs-x402) cited Coinbase's 50 million transaction claim for Agentic Wallets, which helps bracket how quickly paid agent traffic scaled.","values":[50000000]}],"series":["transactions"],"title":"x402 cumulative transaction milestones by March 2026","unit":"transactions"}],"chartsArtifact":{"byteLength":2761,"fileName":"charts.json","format":"charts","mimeType":"application/json; charset=utf-8","sha256":"d2e96e9d16f2b02d5eb43f8f687a52f9d9861e60a383eadc26d487855ab0dcba"},"definition":null,"definitionArtifact":null,"dataset":{"sampleRows":[{"surface":"MCP","primaryLayer":"tool and context interface","paymentRole":"none natively","overlapsWith":"remote tools, agent clients, paid-tool wrappers","whyNotDirectCompetitor":"MCP defines how agents connect to tools, not how money moves."},{"surface":"x402","primaryLayer":"HTTP payment negotiation standard","paymentRole":"challenge, pay, retry, receipt","overlapsWith":"paid APIs, facilitators, agent commerce gateways","whyNotDirectCompetitor":"x402 standardizes the paid-request handshake, not wallet UX or chain-specific operator workflows."},{"surface":"Tempo","primaryLayer":"settlement rail plus operator wallet","paymentRole":"fast settlement, spend controls, service discovery, paid-request tooling","overlapsWith":"MPP-native paid HTTP and agent request flows","whyNotDirectCompetitor":"Tempo wraps payments into an opinionated execution surface rather than stopping at the protocol boundary."},{"surface":"x402 plus MCP bridges","primaryLayer":"monetized tool integration pattern","paymentRole":"turns paid HTTP services into agent-usable tool calls","overlapsWith":"Oops!402, x402-proxy, and similar wrappers","whyNotDirectCompetitor":"These bridges prove the layers compose; they do not collapse them into one category."},{"surface":"Temporal / temporal.rest","primaryLayer":"research and commerce application layer","paymentRole":"packages reports, previews, and machine-readable endpoints as purchasable products","overlapsWith":"Tempo rails, x402-style payment gating, and MCP-shaped agent access patterns","whyNotDirectCompetitor":"Temporal is the product layer buyers interact with, not the base protocol standard or tool-transport spec."}],"summary":{"deepResearchRuns":1,"normalizedSources":72,"publicSources":8,"sampleRows":5,"searchQueries":4,"window":"March 2026"}},"evidence":{"chartProvenance":[{"chartTitle":"x402 daily transaction surge in late October 2025","sourceLabels":["Panewslab x402 surge"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"],"whyUseful":"Turns the report's adoption argument into a measured usage curve instead of a conceptual protocol comparison."},{"chartTitle":"x402 cumulative transaction milestones by March 2026","sourceLabels":["Panewslab x402 surge","O-mega Tempo guide","DeFiPrime MPP vs x402"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09","https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026","https://defiprime.com/stripe-mpp-vs-x402"],"whyUseful":"Shows how quickly paid-agent traffic and settled value accumulated after launch, which matters more to buyers than launch timing alone."}],"claims":[{"chartTitles":[],"confidence":"high","id":"layer-boundary-mcp","kind":"finding","section":"Layer boundaries","sourceLabels":["MCP specification","x402 welcome"],"sourceUrls":["https://modelcontextprotocol.io/specification/2025-06-18","https://docs.cdp.coinbase.com/x402/welcome"],"statement":"MCP remains the tool and context transport layer and does not define native pricing or settlement."},{"chartTitles":[],"confidence":"high","id":"x402-http-handshake","kind":"finding","section":"Paid HTTP handshake","sourceLabels":["x402 welcome","MCP Server with x402"],"sourceUrls":["https://docs.cdp.coinbase.com/x402/welcome","https://docs.cdp.coinbase.com/x402/mcp-server"],"statement":"x402 standardizes the stateless HTTP 402 challenge-pay-retry loop that can sit beneath MCP tools and above a settlement network."},{"chartTitles":[],"confidence":"high","id":"mpp-session-operator-layer","kind":"comparison","section":"Settlement and sessions","sourceLabels":["Tempo Mainnet launch","Privy on Tempo MPP","Alchemy x402 vs MPP"],"sourceUrls":["https://tempo.xyz/blog/mainnet","https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol","https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"],"statement":"Tempo Mainnet and MPP extend the stack with sessions, broader payment-method coverage, and operator-facing controls rather than replacing x402's negotiation layer."},{"chartTitles":[],"confidence":"medium","id":"composition-pattern-production","kind":"comparison","section":"Composition pattern","sourceLabels":["MCP Server with x402","Vercel x402-mcp","Tempo Mainnet launch"],"sourceUrls":["https://docs.cdp.coinbase.com/x402/mcp-server","https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools","https://tempo.xyz/blog/mainnet"],"statement":"The strongest production signal is composition: paid MCP tooling is already combining tool connectivity, paid HTTP, and settlement-oriented rails instead of collapsing them into one protocol."},{"chartTitles":["x402 daily transaction surge in late October 2025"],"confidence":"medium","id":"x402-daily-surge","kind":"chart","section":"Adoption and scale","sourceLabels":["Panewslab x402 surge"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"],"statement":"Public x402 volume reporting moved from roughly 1,000 daily transactions on October 23, 2025 to about 300,000 by October 26, turning the protocol from a spec story into a usage story."},{"chartTitles":["x402 cumulative transaction milestones by March 2026"],"confidence":"medium","id":"x402-cumulative-milestones","kind":"market","section":"Adoption and scale","sourceLabels":["Panewslab x402 surge","O-mega Tempo guide","DeFiPrime MPP vs x402"],"sourceUrls":["https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09","https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026","https://defiprime.com/stripe-mpp-vs-x402"],"statement":"Cumulative public x402 activity reached 1.446 million transactions by late October 2025 and was cited in March 2026 reporting at roughly 140 million transactions after nine months in market."}],"generatedAt":"2026-03-22T00:00:00.000Z","slug":"tempo-x402-mcp-commerce-stack-2026-03","summary":{"chartBackedClaimCount":2,"claimCount":6,"ecosystemSourceCount":6,"officialSourceCount":5,"totalSourceCount":11},"title":"Tempo, x402, and the MCP Commerce Stack"},"evidenceArtifact":{"byteLength":5379,"fileName":"evidence.json","format":"evidence","mimeType":"application/json; charset=utf-8","sha256":"9cc24ac778f24807f3b5408422ede9ab4cdb42b8bb57ebb34fd9e470a1b1d971"},"findings":["MCP is the connectivity layer for tools, resources, and prompts; it does not define pricing or settlement.","x402 standardizes a stateless HTTP 402 payment handshake that can sit beneath MCP-hosted tools and above a settlement network.","Tempo Mainnet and MPP extend the machine-payments stack with settlement characteristics, sessions, and operator-facing payment controls as of March 18, 2026.","The strongest market signal is composition: paid MCP tooling tends to pair a connectivity layer with a payment handshake and a settlement substrate rather than collapsing them into one protocol."],"markdownArtifact":{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/markdown","byteLength":17342,"description":"Narrative positioning memo with stack diagrams, category boundaries, buyer guidance, and appendix notes.","format":"markdown","label":"Full markdown report","mimeType":"text/markdown; charset=utf-8","priceUsdc":0,"sha256":"40377a9ab5d71a003c6b92160b91f2e7c306773269015cf17a10364248a7c003","status":"live"},"markdownAvailable":true,"methodologyArtifact":{"byteLength":1043,"fileName":"methodology.json","format":"methodology","mimeType":"application/json; charset=utf-8","sha256":"d2e0f3c9a2ddd5f2c24d778153be91f1b80c8d9251602df3045dc2b5895510a4"},"methodology":["Anchored the report in official documentation from Tempo, x402, and the Model Context Protocol, with absolute dates as of March 21, 2026.","Used a Perplexity deep-research pass plus focused search queries to gather public examples, then filtered out irrelevant Tempo and MCP references.","Preferred official specifications and launch documentation whenever secondary analysis disagreed or overstated the overlap.","Mapped each protocol to a distinct buyer decision: tool connectivity, payment negotiation, or settlement and operator control."],"outline":[{"id":"tempo-x402-and-the-mcp-commerce-stack","level":1,"text":"Tempo, x402, and the MCP Commerce Stack"},{"id":"layer-1-mcp-the-tool-and-context-interface","level":2,"text":"Layer 1: MCP — The Tool and Context Interface"},{"id":"layer-2-x402-the-paid-http-handshake","level":2,"text":"Layer 2: x402 — The Paid-HTTP Handshake"},{"id":"layer-3-tempo-and-mpp-settlement-sessions-and-operator-controls","level":2,"text":"Layer 3: Tempo and MPP — Settlement, Sessions, and Operator Controls"},{"id":"the-composition-pattern-x402-aware-mcp-servers","level":2,"text":"The Composition Pattern: x402-Aware MCP Servers"},{"id":"comparison-table","level":2,"text":"Comparison Table"},{"id":"decision-guidance-for-buyers","level":2,"text":"Decision Guidance for Buyers"},{"id":"step-1-start-with-the-tool-interface","level":3,"text":"Step 1: Start with the tool interface"},{"id":"step-2-add-the-payment-trigger","level":3,"text":"Step 2: Add the payment trigger"},{"id":"step-3-evaluate-settlement-and-operator-controls","level":3,"text":"Step 3: Evaluate settlement and operator controls"},{"id":"when-to-use-both","level":3,"text":"When to use both"},{"id":"caveats-and-open-questions","level":2,"text":"Caveats and Open Questions"},{"id":"bottom-line","level":2,"text":"Bottom Line"}],"previewMarkdown":"# Tempo, x402, and the MCP Commerce Stack\n\n## Thesis\n\n- MCP handles tool and context connectivity, x402 handles the paid HTTP handshake, and Tempo plus MPP handle settlement-oriented machine-payment flows.\n- As of March 21, 2026, public bridge patterns like x402-aware MCP servers show these layers composing in production instead of replacing one another.\n- Buyers should evaluate the stack in order: discovery and tool interface, payment trigger, then settlement and operator controls.\n\n## Buyer takeaway\n\n- Treat MCP as the tool interface layer.\n- Treat x402 as the paid-request handshake.\n- Treat Tempo and MPP as the settlement and operator-controls layer.\n\nThe full report expands this into a comparison framework, integration patterns, and decision guidance.\n","report":{"category":"Market positioning","datasetSummary":{"deepResearchRuns":1,"normalizedSources":72,"publicSources":8,"sampleRows":5,"searchQueries":4,"window":"March 2026"},"featureKey":"deep_reports_tempo_x402_mcp_commerce_stack_2026_03","findings":["MCP is the connectivity layer for tools, resources, and prompts; it does not define pricing or settlement.","x402 standardizes a stateless HTTP 402 payment handshake that can sit beneath MCP-hosted tools and above a settlement network.","Tempo Mainnet and MPP extend the machine-payments stack with settlement characteristics, sessions, and operator-facing payment controls as of March 18, 2026.","The strongest market signal is composition: paid MCP tooling tends to pair a connectivity layer with a payment handshake and a settlement substrate rather than collapsing them into one protocol."],"methodology":["Anchored the report in official documentation from Tempo, x402, and the Model Context Protocol, with absolute dates as of March 21, 2026.","Used a Perplexity deep-research pass plus focused search queries to gather public examples, then filtered out irrelevant Tempo and MCP references.","Preferred official specifications and launch documentation whenever secondary analysis disagreed or overstated the overlap.","Mapped each protocol to a distinct buyer decision: tool connectivity, payment negotiation, or settlement and operator control."],"previewBullets":["MCP handles tool and context connectivity, x402 handles the paid HTTP handshake, and Tempo plus MPP handle settlement-oriented machine-payment flows.","As of March 21, 2026, public bridge patterns like x402-aware MCP servers show these layers composing in production instead of replacing one another.","Buyers should evaluate the stack in order: discovery and tool interface, payment trigger, then settlement and operator controls."],"publishedAt":"2026-03-21T00:00:00.000Z","sampleRows":[{"surface":"MCP","primaryLayer":"tool and context interface","paymentRole":"none natively","overlapsWith":"remote tools, agent clients, paid-tool wrappers","whyNotDirectCompetitor":"MCP defines how agents connect to tools, not how money moves."},{"surface":"x402","primaryLayer":"HTTP payment negotiation standard","paymentRole":"challenge, pay, retry, receipt","overlapsWith":"paid APIs, facilitators, agent commerce gateways","whyNotDirectCompetitor":"x402 standardizes the paid-request handshake, not wallet UX or chain-specific operator workflows."},{"surface":"Tempo","primaryLayer":"settlement rail plus operator wallet","paymentRole":"fast settlement, spend controls, service discovery, paid-request tooling","overlapsWith":"MPP-native paid HTTP and agent request flows","whyNotDirectCompetitor":"Tempo wraps payments into an opinionated execution surface rather than stopping at the protocol boundary."},{"surface":"x402 plus MCP bridges","primaryLayer":"monetized tool integration pattern","paymentRole":"turns paid HTTP services into agent-usable tool calls","overlapsWith":"Oops!402, x402-proxy, and similar wrappers","whyNotDirectCompetitor":"These bridges prove the layers compose; they do not collapse them into one category."},{"surface":"Temporal / temporal.rest","primaryLayer":"research and commerce application layer","paymentRole":"packages reports, previews, and machine-readable endpoints as purchasable products","overlapsWith":"Tempo rails, x402-style payment gating, and MCP-shaped agent access patterns","whyNotDirectCompetitor":"Temporal is the product layer buyers interact with, not the base protocol standard or tool-transport spec."}],"slug":"tempo-x402-mcp-commerce-stack-2026-03","sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post covering Tempo Mainnet and the public positioning of MPP.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and mainnet integration.","url":"https://docs.tempo.xyz/"},{"kind":"official","label":"x402 welcome","note":"Canonical x402 overview covering the HTTP 402 flow, payment proof, and facilitator model.","url":"https://docs.cdp.coinbase.com/x402/welcome"},{"kind":"official","label":"MCP specification","note":"June 2025 MCP spec defining tools, resources, prompts, and OAuth-based authorization.","url":"https://modelcontextprotocol.io/specification/2025-06-18"},{"kind":"official","label":"MCP Server with x402","note":"Official Coinbase guide showing how paid x402 endpoints can sit behind MCP tools.","url":"https://docs.cdp.coinbase.com/x402/mcp-server"},{"kind":"ecosystem","label":"Vercel x402-mcp","note":"Production bridge pattern that combines MCP tooling with x402-paid resources.","url":"https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Explains how MPP extends request-based payments with sessions and broader payment-method support.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Technical comparison that helps clarify where x402 ends and MPP starts.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Panewslab x402 surge","note":"Late-October 2025 reporting on x402scan daily and cumulative transaction growth.","url":"https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"},{"kind":"ecosystem","label":"O-mega Tempo guide","note":"March 2026 guide citing x402 cumulative transactions and settled volume milestones.","url":"https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026"},{"kind":"ecosystem","label":"DeFiPrime MPP vs x402","note":"Public comparison used here for the Coinbase 50 million transaction claim and protocol framing.","url":"https://defiprime.com/stripe-mpp-vs-x402"}],"subtitle":"Category clarity for buyers deciding where the protocol ends and the product stack begins.","summary":"A positioning report on how Tempo, x402, and MCP-related commerce surfaces fit together across agent tooling, paid HTTP, and operator-facing product layers.","tags":["tempo","x402","mcp","agent-commerce","positioning"],"title":"Tempo, x402, and the MCP Commerce Stack","updatedAt":"2026-03-21T11:40:20.711Z"},"sourcesArtifact":{"byteLength":2911,"fileName":"sources.json","format":"sources","mimeType":"application/json; charset=utf-8","sha256":"f349d9670062576aa3cbfcd604602f8c3e2f6ec7a234c674e695cfdbdff36338"},"sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post covering Tempo Mainnet and the public positioning of MPP.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and mainnet integration.","url":"https://docs.tempo.xyz/"},{"kind":"official","label":"x402 welcome","note":"Canonical x402 overview covering the HTTP 402 flow, payment proof, and facilitator model.","url":"https://docs.cdp.coinbase.com/x402/welcome"},{"kind":"official","label":"MCP specification","note":"June 2025 MCP spec defining tools, resources, prompts, and OAuth-based authorization.","url":"https://modelcontextprotocol.io/specification/2025-06-18"},{"kind":"official","label":"MCP Server with x402","note":"Official Coinbase guide showing how paid x402 endpoints can sit behind MCP tools.","url":"https://docs.cdp.coinbase.com/x402/mcp-server"},{"kind":"ecosystem","label":"Vercel x402-mcp","note":"Production bridge pattern that combines MCP tooling with x402-paid resources.","url":"https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Explains how MPP extends request-based payments with sessions and broader payment-method support.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Technical comparison that helps clarify where x402 ends and MPP starts.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Panewslab x402 surge","note":"Late-October 2025 reporting on x402scan daily and cumulative transaction growth.","url":"https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"},{"kind":"ecosystem","label":"O-mega Tempo guide","note":"March 2026 guide citing x402 cumulative transactions and settled volume milestones.","url":"https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026"},{"kind":"ecosystem","label":"DeFiPrime MPP vs x402","note":"Public comparison used here for the Coinbase 50 million transaction claim and protocol framing.","url":"https://defiprime.com/stripe-mpp-vs-x402"}]},"generatedAt":"2026-05-04T01:22:16.764Z","kind":"deep_report_json"},"methodology":{"artifact":{"byteLength":1043,"fileName":"methodology.json","format":"methodology","mimeType":"application/json; charset=utf-8","sha256":"d2e0f3c9a2ddd5f2c24d778153be91f1b80c8d9251602df3045dc2b5895510a4"},"document":{"category":"Market positioning","datasetSummary":{"deepResearchRuns":1,"normalizedSources":72,"publicSources":8,"sampleRows":5,"searchQueries":4,"window":"March 2026"},"generatedAt":"2026-03-22T00:00:00.000Z","methodology":["Anchored the report in official documentation from Tempo, x402, and the Model Context Protocol, with absolute dates as of March 21, 2026.","Used a Perplexity deep-research pass plus focused search queries to gather public examples, then filtered out irrelevant Tempo and MCP references.","Preferred official specifications and launch documentation whenever secondary analysis disagreed or overstated the overlap.","Mapped each protocol to a distinct buyer decision: tool connectivity, payment negotiation, or settlement and operator control."],"publishedAt":"2026-03-21T00:00:00.000Z","slug":"tempo-x402-mcp-commerce-stack-2026-03","title":"Tempo, x402, and the MCP Commerce Stack","updatedAt":"2026-03-21T11:40:20.711Z"}},"manifest":{"artifactCount":7,"generatedAt":"2026-05-04T01:22:16.764Z","hashAlgorithm":"sha256","includedFormats":["bundle","json","markdown","charts","evidence","methodology","sources"],"slug":"tempo-x402-mcp-commerce-stack-2026-03"},"markdown":{"artifact":{"apiPath":"/api/reports/tempo-x402-mcp-commerce-stack-2026-03/markdown","byteLength":17342,"description":"Narrative positioning memo with stack diagrams, category boundaries, buyer guidance, and appendix notes.","format":"markdown","label":"Full markdown report","mimeType":"text/markdown; charset=utf-8","priceUsdc":0,"sha256":"40377a9ab5d71a003c6b92160b91f2e7c306773269015cf17a10364248a7c003","status":"live"},"content":"# Tempo, x402, and the MCP Commerce Stack\n\n*Category clarity for buyers deciding where the protocol ends and the product stack begins.*\n\n**Published March 21, 2026 — temporal.rest**\n\n---\n\nThe infrastructure for autonomous agent commerce has, as of March 2026, crystallized into a layered stack where three protocols address three distinct problems. The Model Context Protocol (MCP) governs how AI agents discover and invoke tools. The x402 protocol standardizes how an HTTP request can trigger, verify, and settle a payment. Tempo and the Machine Payments Protocol (MPP) provide the settlement rail and the operator-facing controls that give enterprises confidence their agents are spending within policy.\n\nThe strongest market signal is not that one of these standards is winning. It is that they compose. Paid MCP servers running x402-gated endpoints over Tempo settlement are already live in production. For buyers evaluating the landscape, the critical question is therefore not *which protocol to bet on* but *which layer each protocol owns, where the seams are, and what decisions remain at the product level*.\n\nThis report maps those layers, documents how they interlock, and offers decision guidance for teams building or buying agent-commerce infrastructure.\n\n---\n\n## Layer 1: MCP — The Tool and Context Interface\n\nThe [Model Context Protocol](https://modelcontextprotocol.io/specification/2025-06-18), introduced by Anthropic in November 2024 and refined through its June 2025 specification update, standardizes how large language models connect to external data sources, tools, and capabilities. It uses JSON-RPC 2.0 messages carried over a stateful session, and its architecture revolves around three building blocks that servers expose to clients:\n\n- **Resources** — passive, read-only data such as file contents, database schemas, or API responses, each identified by a unique URI ([spec](https://modelcontextprotocol.io/specification/2025-06-18/server/resources)).\n- **Tools** — executable operations with typed inputs and outputs validated via JSON Schema, allowing models to discover and invoke them automatically based on context.\n- **Prompts** — reusable template patterns that let server authors showcase best practices for using their services ([server concepts](https://modelcontextprotocol.io/docs/learn/server-concepts)).\n\nCrucially, **MCP deliberately excludes commerce semantics**. The protocol can expose a tool that returns a price, but it provides no standardized way for that tool to charge for its use or for the calling agent to pay for execution. The June 2025 authorization update added OAuth 2.1-based access controls and Protected Resource Metadata discovery, but these authenticate *who* can access tools — they do not coordinate *payment* for tool use.\n\nThis boundary is strategic. MCP solves the connectivity problem — secure, structured access to capabilities once discovered — and leaves payment to protocols designed for exactly that purpose. By March 2026, MCP adoption has expanded well beyond Claude: the Vercel AI SDK supports MCP clients, and platforms including Shopify and Stripe have begun offering MCP integration points. Every one of these integrations still requires a separate payment mechanism, confirming MCP's role as the tool-interface layer rather than a commerce layer.\n\n**What MCP does not do.** MCP provides no mechanism for an agent to discover that an MCP server exists in the first place (discovery at web scale), no way to embed pricing information in tool metadata, and no settlement or receipt semantics. These are gaps by design, not oversights.\n\n---\n\n## Layer 2: x402 — The Paid-HTTP Handshake\n\nWhere MCP standardizes *how to call a tool*, [x402](https://docs.cdp.coinbase.com/x402/welcome) standardizes *how to pay for a resource within an HTTP request*. Developed by Coinbase and published as an open specification, x402 revives the long-dormant HTTP 402 \"Payment Required\" status code and turns it into a machine-actionable payment flow:\n\n1. The buyer (agent or client) requests a resource.\n2. The server responds with HTTP 402 plus a JSON body describing the payment requirement — amount, asset (typically USDC), recipient address, and a validity window.\n3. The buyer's wallet constructs a one-time signed payment authorization using EIP-3009 (\"Transfer With Authorization\"), avoiding the need for a separate on-chain gas transaction.\n4. The buyer retries the request with the payment proof in an HTTP header.\n5. A [facilitator](https://docs.cdp.coinbase.com/x402/core-concepts/facilitator) — an independent verification and settlement service operated by Coinbase or others — validates the signature, confirms the amount, submits the transaction to the blockchain, and signals the server to release the resource.\n\nThe result is a **stateless, per-request payment handshake** that requires no API keys, billing accounts, or prior customer relationship. It is purpose-built for machine-to-machine microtransactions and API monetization.\n\nx402 also introduced [Bazaar](https://docs.cdp.coinbase.com/x402/bazaar), a discovery layer that lets buyers query a registry of x402-protected endpoints. Bazaar addresses one of MCP's explicit non-goals — finding services at web scale — but only for services that use the x402 payment model.\n\n**What x402 does not do.** x402 stops at the handshake. It does not manage sessions, budget caps, multi-step workflows, operator-level spend controls, or fiat settlement. It also does not prescribe a specific blockchain — though in practice nearly all production x402 deployments as of March 2026 settle on Base using USDC.\n\n---\n\n## Layer 3: Tempo and MPP — Settlement, Sessions, and Operator Controls\n\n[Tempo Mainnet launched on March 18, 2026](https://tempo.xyz/blog/mainnet), alongside the Machine Payments Protocol (MPP), co-developed with Stripe. Tempo is purpose-built payments infrastructure: instant settlement, predictable low fees, high throughput, and global availability. MPP sits atop this infrastructure and extends the machine-payments thesis in several important directions.\n\nAccording to the [Privy integration guide](https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol) and the [Alchemy comparison](https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols), the key architectural differences between MPP and x402 include:\n\n- **Payment-method breadth.** MPP supports multiple payment methods rather than being limited to on-chain stablecoins.\n- **Sessions.** Where x402 is stateless and per-request, MPP introduces a session model that lets an agent open a payment session, execute multiple paid requests within it, and close the session with a single settlement event. This reduces transaction overhead for multi-step agent workflows.\n- **Spend controls and operator policy.** MPP defines operator-facing primitives — budget ceilings, per-session caps, approval gates — that let the human or organization behind an agent govern how much it can spend and on what.\n\n```chart\ntitle: x402 daily transaction surge in late October 2025\ncaption: The strongest factual proof that x402 became more than a whitepaper is usage: public reporting on x402scan showed daily transactions jumping from roughly 1,000 to 300,000 in four days.\nunit: daily transactions\n2025-10-23 | 1000 | [Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) summarized x402scan activity before the late-October surge at roughly one thousand daily transactions.\n2025-10-24 | 100000 | The same report marked October 24 as the first day the ecosystem crossed into six-figure daily transaction territory.\n2025-10-25 | 200000 | Activity roughly doubled again one day later, showing this was not a one-day spike.\n2025-10-26 | 300000 | By October 26, daily volume was reported around 300,000 transactions, making the production-usage case much harder to dismiss.\n```\n\nCritically, [Tempo and MPP explicitly build on the same foundation as x402](https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol). Both use HTTP 402 to signal that a request requires payment. Both enable programmatic, request-based payments within standard HTTP flows. MPP extends this model rather than replacing it. One developer [reported going live with both x402 and MPP on launch day](https://dev.to/nathanielc85523/i-went-live-with-both-x402-and-mpp-on-launch-day-heres-what-500-agent-probes-taught-me-2j7p) without breaking existing x402 integrations — evidence that the protocols compose rather than conflict.\n\n**What Tempo and MPP do not do.** Neither protocol defines how an agent discovers tools or negotiates capability metadata. That remains MCP's domain. And while MPP's session model adds statefulness, it does not attempt to replace MCP's structured tool-invocation semantics.\n\n---\n\n## The Composition Pattern: x402-Aware MCP Servers\n\nThe most important architecture emerging in production as of March 2026 is the **x402-aware MCP server** — a pattern that wires all three layers together without collapsing them.\n\n[Coinbase's official documentation](https://docs.cdp.coinbase.com/x402/mcp-server) provides a reference integration showing how to run an MCP server whose tools are gated behind x402 payment requirements. [Vercel's x402-mcp library](https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools) packages this further, letting any MCP server declare tool prices and accept x402 payments within the Vercel AI SDK.\n\nThe flow works as follows:\n\n1. An agent connects to an MCP server and discovers available tools via standard MCP capability negotiation.\n2. The agent invokes a tool — say, \"premium-search.\"\n3. The MCP server proxies the request to an x402-protected HTTP endpoint.\n4. The endpoint returns a 402 with payment requirements.\n5. The agent's wallet (configured via an environment variable or key-management service like Privy) constructs a signed payment authorization.\n6. The request is retried with the payment header; the facilitator settles the payment; the tool returns its result to the agent.\n\nCommunity implementations such as the [spot-402-mcp-server on LobeHub](https://lobehub.com/mcp/spot-402-mcp-server) and tutorials like [Monetizing MCP Servers with x402](https://www.youtube.com/watch?v=exxnhnFHqAw&vl=ja) confirm this pattern is reproducible across frameworks.\n\nWhen Tempo and MPP are added to this stack, the settlement layer gains sessions and operator controls. An enterprise deploying agents can configure budget policies at the Tempo layer while the MCP interface and x402 handshake remain unchanged at the tool and payment layers.\n\n```chart\nchartType: bar\ntitle: x402 cumulative transaction milestones by March 2026\ncaption: The other useful question for buyers is not just whether x402 launched, but how much paid traffic and settled value accumulated after launch.\nunit: transactions\nOct 26, 2025 cumulative | 1446000 | [Panewslab](https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09) reported 1.446 million cumulative x402 transactions and about $1.59 million in settled volume after the first late-October burst.\nNine months in market | 140000000 | [O-mega.ai](https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026) cited roughly 140 million transactions and $43 million in settled volume within nine months.\nCoinbase public claim | 50000000 | [DeFiPrime](https://defiprime.com/stripe-mpp-vs-x402) cited Coinbase's 50 million transaction claim for Agentic Wallets, which helps bracket how quickly paid agent traffic scaled.\n```\n\n---\n\n## Comparison Table\n\n| Dimension | MCP | x402 | Tempo / MPP |\n|---|---|---|---|\n| **Primary layer** | Tool and context interface | HTTP payment negotiation | Settlement rail + operator controls |\n| **Core specification** | [MCP spec (June 2025)](https://modelcontextprotocol.io/specification/2025-06-18) | [x402 docs](https://docs.cdp.coinbase.com/x402/welcome) | [Tempo docs](https://docs.tempo.xyz/) |\n| **Payment role** | None natively | Challenge → pay → retry → receipt | Settlement, sessions, spend caps, multi-method |\n| **Statefulness** | Stateful session (JSON-RPC) | Stateless per-request | Session-based (MPP sessions) |\n| **Discovery** | Server-to-client capability listing | Bazaar registry | MPP service discovery |\n| **Auth model** | OAuth 2.1 (who can access) | Cryptographic payment proof (pay to access) | Operator budget policy + payment auth |\n| **Settlement** | N/A | On-chain (primarily USDC on Base) | On-chain (Tempo Mainnet) + Stripe fiat rails |\n| **Agent SDK support** | Vercel AI SDK, Claude, others | LangChain (x402-langchain), Vercel | Stripe SDK, Privy, Parallel APIs |\n| **What it deliberately excludes** | Pricing, settlement, receipts | Sessions, budget caps, fiat rails | Tool metadata, capability negotiation |\n\n---\n\n## Decision Guidance for Buyers\n\n### Step 1: Start with the tool interface\n\nIf your agents need to discover and invoke third-party tools, MCP is the connectivity standard to adopt. It is vendor-neutral, multi-platform, and supported by major LLM providers. Evaluate MCP server frameworks (Vercel AI SDK, Cloudflare Workers, MCP-Go) based on your runtime environment.\n\n### Step 2: Add the payment trigger\n\nIf any of those tools should be paid per-request — and the service provider uses or plans to use HTTP 402-based gating — adopt x402 client support. This is a lightweight addition: an x402-aware HTTP client or MCP wrapper intercepts 402 responses, constructs payment proofs, and retries. The [Coinbase x402 SDK](https://docs.cdp.coinbase.com/x402/welcome) and community wrappers make this a single dependency addition.\n\n### Step 3: Evaluate settlement and operator controls\n\nFor organizations that need session-based billing, budget governance, fiat settlement options, or compliance-friendly audit trails, Tempo and MPP add the operator layer. The decision between x402-only and MPP depends on:\n\n- **Transaction volume.** If agents make many small requests within a workflow, MPP's session model reduces per-request overhead.\n- **Payment-method requirements.** If buyers or sellers need fiat settlement (via Stripe), MPP supports this natively; x402 alone does not.\n- **Spend governance.** If a finance team needs to cap agent spending per day, per session, or per vendor, MPP's operator controls are purpose-built for this. x402 has no equivalent.\n- **Chain flexibility.** As of March 21, 2026, x402 production deployments overwhelmingly settle on Base. Tempo settles on its own mainnet. Evaluate based on your treasury and compliance posture.\n\n### When to use both\n\nThe strongest evidence from production deployments is that x402 and MPP are not either/or. MPP is designed to layer atop x402 infrastructure. Teams that adopted x402 early can add MPP without rewriting their payment integration. The [launch-day dual-deployment report](https://dev.to/nathanielc85523/i-went-live-with-both-x402-and-mpp-on-launch-day-heres-what-500-agent-probes-taught-me-2j7p) confirms backward compatibility.\n\n---\n\n## Caveats and Open Questions\n\n- **MCP payment semantics remain undefined.** As of March 21, 2026, the MCP specification includes no native pricing, payment, or receipt primitives. x402-MCP bridges exist as community and vendor integrations (Coinbase, Vercel, LobeHub), not as part of the MCP standard itself. Whether a future MCP revision will standardize payment metadata is an open question.\n- **MPP is still at launch-stage maturity.** Tempo Mainnet and MPP launched on March 18, 2026. That means the protocol direction is now public and credible, but long-term interoperability, tooling quality, and production depth still need more time in market than x402's earlier request-handshake model.\n- **Discovery remains fragmented.** MCP discovers capabilities only after a server is known. Bazaar discovers payable x402 endpoints. Tempo and MPP maintain their own service surfaces. Buyers should expect to assemble discovery, invocation, and payment policy as separate product concerns for now.\n- **Settlement remains a product choice, not a protocol inevitability.** As of March 21, 2026, x402 is strongly associated with Base and USDC in production, while MPP is strongly associated with Tempo and Stripe-backed multi-method flows. That may change over time, but teams making platform bets today still need an explicit treasury, compliance, and latency view.\n\n---\n\n## Bottom Line\n\nThe right way to think about this market is not as a protocol horse race.\n\n- Use **MCP** to let agents discover and invoke tools in a structured, cross-platform way.\n- Use **x402** when you need a clean, stateless HTTP-native payment handshake for paid resources.\n- Use **Tempo and MPP** when you need a settlement rail plus operator controls, sessions, and broader payment-method flexibility for agent commerce.\n\nThe buyer error is to collapse those layers into one category because they show up in the same demo. The market reality, as of March 21, 2026, is that they are becoming more complementary, not less. Teams that understand that layering can adopt each part of the stack on its own merits, swap pieces without rewriting the full system, and package the result into a product that humans and agents can actually trust.\n"},"previewMarkdown":"# Tempo, x402, and the MCP Commerce Stack\n\n## Thesis\n\n- MCP handles tool and context connectivity, x402 handles the paid HTTP handshake, and Tempo plus MPP handle settlement-oriented machine-payment flows.\n- As of March 21, 2026, public bridge patterns like x402-aware MCP servers show these layers composing in production instead of replacing one another.\n- Buyers should evaluate the stack in order: discovery and tool interface, payment trigger, then settlement and operator controls.\n\n## Buyer takeaway\n\n- Treat MCP as the tool interface layer.\n- Treat x402 as the paid-request handshake.\n- Treat Tempo and MPP as the settlement and operator-controls layer.\n\nThe full report expands this into a comparison framework, integration patterns, and decision guidance.\n","report":{"category":"Market positioning","datasetSummary":{"deepResearchRuns":1,"normalizedSources":72,"publicSources":8,"sampleRows":5,"searchQueries":4,"window":"March 2026"},"featureKey":"deep_reports_tempo_x402_mcp_commerce_stack_2026_03","findings":["MCP is the connectivity layer for tools, resources, and prompts; it does not define pricing or settlement.","x402 standardizes a stateless HTTP 402 payment handshake that can sit beneath MCP-hosted tools and above a settlement network.","Tempo Mainnet and MPP extend the machine-payments stack with settlement characteristics, sessions, and operator-facing payment controls as of March 18, 2026.","The strongest market signal is composition: paid MCP tooling tends to pair a connectivity layer with a payment handshake and a settlement substrate rather than collapsing them into one protocol."],"methodology":["Anchored the report in official documentation from Tempo, x402, and the Model Context Protocol, with absolute dates as of March 21, 2026.","Used a Perplexity deep-research pass plus focused search queries to gather public examples, then filtered out irrelevant Tempo and MCP references.","Preferred official specifications and launch documentation whenever secondary analysis disagreed or overstated the overlap.","Mapped each protocol to a distinct buyer decision: tool connectivity, payment negotiation, or settlement and operator control."],"previewBullets":["MCP handles tool and context connectivity, x402 handles the paid HTTP handshake, and Tempo plus MPP handle settlement-oriented machine-payment flows.","As of March 21, 2026, public bridge patterns like x402-aware MCP servers show these layers composing in production instead of replacing one another.","Buyers should evaluate the stack in order: discovery and tool interface, payment trigger, then settlement and operator controls."],"publishedAt":"2026-03-21T00:00:00.000Z","sampleRows":[{"surface":"MCP","primaryLayer":"tool and context interface","paymentRole":"none natively","overlapsWith":"remote tools, agent clients, paid-tool wrappers","whyNotDirectCompetitor":"MCP defines how agents connect to tools, not how money moves."},{"surface":"x402","primaryLayer":"HTTP payment negotiation standard","paymentRole":"challenge, pay, retry, receipt","overlapsWith":"paid APIs, facilitators, agent commerce gateways","whyNotDirectCompetitor":"x402 standardizes the paid-request handshake, not wallet UX or chain-specific operator workflows."},{"surface":"Tempo","primaryLayer":"settlement rail plus operator wallet","paymentRole":"fast settlement, spend controls, service discovery, paid-request tooling","overlapsWith":"MPP-native paid HTTP and agent request flows","whyNotDirectCompetitor":"Tempo wraps payments into an opinionated execution surface rather than stopping at the protocol boundary."},{"surface":"x402 plus MCP bridges","primaryLayer":"monetized tool integration pattern","paymentRole":"turns paid HTTP services into agent-usable tool calls","overlapsWith":"Oops!402, x402-proxy, and similar wrappers","whyNotDirectCompetitor":"These bridges prove the layers compose; they do not collapse them into one category."},{"surface":"Temporal / temporal.rest","primaryLayer":"research and commerce application layer","paymentRole":"packages reports, previews, and machine-readable endpoints as purchasable products","overlapsWith":"Tempo rails, x402-style payment gating, and MCP-shaped agent access patterns","whyNotDirectCompetitor":"Temporal is the product layer buyers interact with, not the base protocol standard or tool-transport spec."}],"slug":"tempo-x402-mcp-commerce-stack-2026-03","sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post covering Tempo Mainnet and the public positioning of MPP.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and mainnet integration.","url":"https://docs.tempo.xyz/"},{"kind":"official","label":"x402 welcome","note":"Canonical x402 overview covering the HTTP 402 flow, payment proof, and facilitator model.","url":"https://docs.cdp.coinbase.com/x402/welcome"},{"kind":"official","label":"MCP specification","note":"June 2025 MCP spec defining tools, resources, prompts, and OAuth-based authorization.","url":"https://modelcontextprotocol.io/specification/2025-06-18"},{"kind":"official","label":"MCP Server with x402","note":"Official Coinbase guide showing how paid x402 endpoints can sit behind MCP tools.","url":"https://docs.cdp.coinbase.com/x402/mcp-server"},{"kind":"ecosystem","label":"Vercel x402-mcp","note":"Production bridge pattern that combines MCP tooling with x402-paid resources.","url":"https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Explains how MPP extends request-based payments with sessions and broader payment-method support.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Technical comparison that helps clarify where x402 ends and MPP starts.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Panewslab x402 surge","note":"Late-October 2025 reporting on x402scan daily and cumulative transaction growth.","url":"https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"},{"kind":"ecosystem","label":"O-mega Tempo guide","note":"March 2026 guide citing x402 cumulative transactions and settled volume milestones.","url":"https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026"},{"kind":"ecosystem","label":"DeFiPrime MPP vs x402","note":"Public comparison used here for the Coinbase 50 million transaction claim and protocol framing.","url":"https://defiprime.com/stripe-mpp-vs-x402"}],"subtitle":"Category clarity for buyers deciding where the protocol ends and the product stack begins.","summary":"A positioning report on how Tempo, x402, and MCP-related commerce surfaces fit together across agent tooling, paid HTTP, and operator-facing product layers.","tags":["tempo","x402","mcp","agent-commerce","positioning"],"title":"Tempo, x402, and the MCP Commerce Stack","updatedAt":"2026-03-21T11:40:20.711Z"},"sources":{"artifact":{"byteLength":2911,"fileName":"sources.json","format":"sources","mimeType":"application/json; charset=utf-8","sha256":"f349d9670062576aa3cbfcd604602f8c3e2f6ec7a234c674e695cfdbdff36338"},"document":{"counts":{"ecosystem":6,"official":5,"total":11},"generatedAt":"2026-03-22T00:00:00.000Z","slug":"tempo-x402-mcp-commerce-stack-2026-03","sources":[{"kind":"official","label":"Tempo Mainnet launch","note":"March 18, 2026 launch post covering Tempo Mainnet and the public positioning of MPP.","url":"https://tempo.xyz/blog/mainnet"},{"kind":"official","label":"Tempo docs","note":"Official developer docs for wallets, payments, and mainnet integration.","url":"https://docs.tempo.xyz/"},{"kind":"official","label":"x402 welcome","note":"Canonical x402 overview covering the HTTP 402 flow, payment proof, and facilitator model.","url":"https://docs.cdp.coinbase.com/x402/welcome"},{"kind":"official","label":"MCP specification","note":"June 2025 MCP spec defining tools, resources, prompts, and OAuth-based authorization.","url":"https://modelcontextprotocol.io/specification/2025-06-18"},{"kind":"official","label":"MCP Server with x402","note":"Official Coinbase guide showing how paid x402 endpoints can sit behind MCP tools.","url":"https://docs.cdp.coinbase.com/x402/mcp-server"},{"kind":"ecosystem","label":"Vercel x402-mcp","note":"Production bridge pattern that combines MCP tooling with x402-paid resources.","url":"https://vercel.com/blog/introducing-x402-mcp-open-protocol-payments-for-mcp-tools"},{"kind":"ecosystem","label":"Privy on Tempo MPP","note":"Explains how MPP extends request-based payments with sessions and broader payment-method support.","url":"https://privy.io/blog/building-on-privy-with-tempo-machine-payments-protocol"},{"kind":"ecosystem","label":"Alchemy x402 vs MPP","note":"Technical comparison that helps clarify where x402 ends and MPP starts.","url":"https://www.alchemy.com/blog/x402-vs-mpp-comparing-agent-payment-protocols"},{"kind":"ecosystem","label":"Panewslab x402 surge","note":"Late-October 2025 reporting on x402scan daily and cumulative transaction growth.","url":"https://www.panewslab.com/en/articles/7c3be5b3-b0de-4405-adbd-af9a16d4ae09"},{"kind":"ecosystem","label":"O-mega Tempo guide","note":"March 2026 guide citing x402 cumulative transactions and settled volume milestones.","url":"https://o-mega.ai/articles/tempo-and-agentic-payments-the-complete-guide-2026"},{"kind":"ecosystem","label":"DeFiPrime MPP vs x402","note":"Public comparison used here for the Coinbase 50 million transaction claim and protocol framing.","url":"https://defiprime.com/stripe-mpp-vs-x402"}],"title":"Tempo, x402, and the MCP Commerce Stack"}}},"generatedAt":"2026-05-04T01:22:16.764Z","kind":"deep_report_bundle","operatorAccess":null,"payer":null}