{"artifact":{"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"},"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"},"generatedAt":"2026-05-04T00:14:34.290Z","kind":"deep_report_methodology","operatorAccess":null,"payer":null}