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 OCTOBER 18, 2026
MPP syncs its docs to mppx 0.13.4 and hardens CI while AIsa's listing waits on confirmed payment.
No new MPP integration, payment term, or protocol capability verified this week. The SDK docs caught up to mppx 0.13.4, AIsa joined the service catalog as a fixed-price listing that accepts challenges but hasn't shown a confirmed payment, and the repositories spent the week on GitHub Actions pins, a Dependabot cooldown fix, and corrections to proxy and skill discovery paths.
Signal No verified new development; the week's activity was documentation, CI maintenance, and one unconfirmed catalog addition.
Evidence SDK docs synced to mppx 0.13.4; AIsa's fixed-price data APIs listed but end-to-end payment unconfirmed; GitHub Actions references pinned to commit 947d9a3c; cooldown extended from seven to eight days to fix a Dependabot tag-date issue; proxy discovery docs corrected to /openapi.json and /llms.txt; skill publication moved to canonical files under /.well-known/agent-skills/.
Watch next Whether AIsa shows a verifiable Credential → execution → Receipt cycle, whether the eight-day cooldown change stops the Dependabot timing issue it targets, and whether the corrected discovery paths return what the docs now claim.
Read last week's report — MPP adds Apify and a first-party Tempo API while clearing ten dead listings.
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.