Sato Hub
← Back to directory
API / SDKActiveUnverifiedActive · 2d ago

Tempo MPP Specs

Specification for the Payment HTTP auth scheme (Multi-Party Payments) from Tempo, the Stripe/Paradigm-backed payments L1.

Last release Jul 17, 2026

Overview

This repo publishes the specification for Tempo's Machine Payments Protocol, an HTTP 'Payment' authentication scheme for machine-to-machine payments, positioned alongside x402 as an emerging standard some agent-payment SDKs are starting to implement. It's a specs repo, not a runnable library — builders use it as a reference when implementing MPP support. 85 GitHub stars, active.

Sato Score

56/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
16/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
5/15
Independent verification
0/10

Details

Chains
Multichain
Agent types
Payment protocol specification
Open source
Yes
Last checked
2026-07-19

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#payments-protocol#specification#x402-adjacent#standards

Where Tempo MPP Specs fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Tempo MPP Specs, pulled from its GitHub and X.

Listing History

Recorded changes to Tempo MPP Specs's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 19, 2026
    Edited: chains supported
  2. Jul 19, 2026
    Listed on Sato Hub
  3. Jul 19, 2026
    Sato Hub began tracking this listing

Related Resources

Join the Sato Hub Briefing

One email a week — the agents, tools, and infrastructure that actually shipped, and why they matter.