A primary-source review of MPP, Payment Auth, Tempo and HTTP 402 for the week ending November 22, 2026.
The last published brief (week ending November 8) was two straight weeks of zero verified developments — AGENTS.md harmonization, a close-supervision schedule, dependency patches. This week’s primary record still shows no new MPP integration, payment term, or protocol capability. But it’s a denser week than either of those two: the facilitator guide sellers actually read got simpler and gained a live testnet URL, NEAR Intents wrote down its refund rules, the service directory picked up two new proxies while restoring a tag it had dropped, the playground learned to screen for compliance, and the deploy pipeline stopped depending on a static token. None of it is adoption news. All of it is the kind of groundwork that adoption news eventually depends on.
The Tempo x402 facilitator guide gets simpler, and the testnet URL goes live
mpp PR #1255 first added a dedicated Tempo facilitator section to the x402 guide, with its commit, and PR #1262 then simplified that guide down to its essential steps, via its commit — per this week’s record, the guide now covers Python alongside its existing language support. Separately, PR #1260 clarified that settling a payment returns the Tempo payout hash directly, with no polling needed, through its commit. And PR #1264 linked a live Tempo x402 testnet facilitator URL, with its commit.
Taken together, these four PRs are the clearest seller-facing improvement in weeks: fewer steps to read, a direct answer instead of a polling loop, and an actual endpoint to point at instead of a placeholder. That’s still a documentation and reachability change, not a verified integration — what’s worth testing next, per the source report, is running the simplified guide end-to-end against the live testnet URL and confirming the payout hash comes back exactly as the new docs describe, for a seller who’s never touched the flow before.
NEAR Intents writes down its refund resolver and -01 settlement rules
mpp PR #1269 documented the NEAR Intents refund resolver and the -01 settlement rules, with its commit.
This is the kind of documentation that matters because of what it unlocks rather than what it ships: a documented refund resolver means a payer has a defined path to get money back without routing through the original seller. It’s still only a documented path. Worth verifying next, per the source report, is whether the refund resolver actually works as written in a test environment — a refund mechanism that’s correct on paper and untested in practice is the one gap in this guide that would matter most if it’s wrong.
A leaner service directory, with first-party tagging back and two new proxies
mpp PR #1247 restored the directory’s first-party tag and simplified its payment filters, with its commit. Two proxies joined the catalog alongside it: PR #1266 listed Bright Data, with its commit, and PR #1259 listed MillionVerifier, with its commit, followed by PR #1265 adding MillionVerifier’s icon. Two performance changes touched the same page: PR #1246 now renders endpoint tables only on first expand, with its commit, and PR #1245 switched logos to static WebP, with its commit. Rounding it out, PR #1267 added a health check probing Bright Data’s own unlock route, with its commit.
A catalog listing is still just a listing — being in the directory means a proxy is documented and reachable, not that anyone’s traffic is routed through it yet. First-party tagging restored is the one worth flagging on its own: a directory that mislabels first-party services is worse than one with no tag at all, since it actively misleads rather than simply omitting information. Per the source report, what’s worth confirming next is that Bright Data and MillionVerifier show up correctly in the directory and that the new health check against Bright Data’s unlock route actually passes, not just that it was added.
The playground adds a Tempo ID tier, and teaches it to screen for compliance
mpp PR #1256 added a Tempo ID tier to the playground along with a shared MPP Demo Agent, with its commit. PR #1258 fixed how the Tempo ID code is handed back, moving it onto a BroadcastChannel, via its commit, and PR #1257 switched the playground to use the registered Tempo ID app so compliance screening runs for real, with its commit.
This is the playground becoming a more honest test bed, not a new production capability — a shared demo agent and a registered app mean the compliance screening path being exercised is closer to what a real integration would hit. Worth verifying next, per the source report, is whether the Tempo ID tier actually enforces compliance screening consistently and shows accurate state across a session, rather than only on the first pass.
Deployment drops its static Cloudflare token
mpp PR #1272 moved deployment to Cloudflare’s Deploy Broker instead of a static CLOUDFLARE_API_TOKEN, with its commit, and the companion PR #1273 granted id-token: write to the deploy workflow’s check job so the broker’s OIDC exchange can actually run, with its commit.
Removing a long-lived static token from CI is a real security improvement regardless of whether anyone outside the project notices it — it’s the kind of change that only shows up in an incident report when it’s skipped, not when it’s done. Per the source report, what’s worth confirming is that the broker-based deploy actually succeeds cleanly on the next push to main, since a credential migration that works in testing but stalls on the first real deploy is a worse failure mode than the token it replaced.
A lighter homepage
mpp PR #1249 lazy-loaded GSAP, shrank the homepage video, and dropped PostHog surveys, with its commit.
Straightforward site performance work aimed at mobile load times, not at anything an integrator would act on. Worth checking, per the source report, is whether these changes hold up under load and across devices rather than just in a single local test.
Community signals, named and not folded in
Two items from this week’s source ledger are independent commentary, not MPP or IETF spec developments, and neither comes with a transaction record to verify independently: NostrPulse, a Bitcoin HTTP 402 (L402 and Cashu) MCP server pitched for AI agents, and a market roundup on who’s selling, passing conformance, and buying in the x402 ecosystem as of November 2026. Both stay signals to watch rather than verified developments.
What I’m taking from this week
Third week running without a new payment term or integration, but the texture is different from the two before it. Those were internal process hygiene; this one touched nearly every surface a seller or integrator would actually hit — the facilitator guide and its testnet URL, a documented refund path, a cleaner and more honestly labeled directory, a playground that screens for compliance instead of faking it, and a deploy pipeline that no longer leans on a static token. None of it should be read as adoption. The honest open questions carry forward directly: whether the simplified facilitator flow and its payout hash behave as documented against the live testnet URL, whether the NEAR Intents refund resolver actually resolves refunds when tested, whether the two new proxies and their health checks hold up past this week’s redeploy, and whether the Tempo ID compliance screening stays consistent across a full session rather than just the first run.
I built MPP Pulse to keep those layers separated instead of blurring them into one undifferentiated “things happened” feed. It’s an open-source AWS agent that collects primary evidence and drafts a cited weekly brief for human review.