Protocols
MPP, Payment Auth, HTTP 402, x402, specifications, and revision-level changes.
SANDBOX LABS AI · RESEARCH BRIEF
MPP Pulse
Weekly intelligence on the machine-payments layer: MPP, Tempo, x402, Payment Auth, HTTP 402, and the infrastructure making agent-to-agent commerce possible.
Subscription interest is reviewed manually. No spam, no automated enrollment.
01
Current Pulse
LATEST BRIEF · WEEK ENDING JULY 19, 2026
Implementation is expanding faster than the public evidence of adoption.
This week's primary-source review follows MPP from the Tempo mainnet launch through July 19: more payment rails, sessions, discovery and security work, but much less verified evidence of production use.
Signal MPP work is widening across rails, session patterns and payment discovery.
Evidence Primary sources show active implementation, not yet broad production adoption.
Watch next Maintained interoperability, transaction evidence and provider retention.
02
What it watches
Implementation
Repository activity, merged pull requests, releases, tags, and verifiable deployment evidence.
Adoption
Official announcements, integrations, payment rails, and machine-commerce infrastructure.
Evidence
Primary sources first. Community discussion is context, never proof by itself.
03
Why it exists
Machine payments are becoming an infrastructure layer for agents. The useful evidence is scattered across specifications, code, company announcements, and developer activity. MPP Pulse turns that movement into a short, cited weekly read.
Sources→Collection→Evidence gates→Human review→Weekly brief
04
Built in public
MPP Pulse began as an always-on AWS agent: EventBridge Scheduler triggers one Lambda; the agent collects, scores, and stores evidence; Amazon Bedrock prepares a cited report. The public project is open source, while the research workflow stays deliberately human-reviewed.