Tempo MPP Specs
Specification for the Payment HTTP auth scheme (Machine Payments Protocol) from Tempo, the Stripe/Paradigm-backed payments L1.
- Sato Score63
- ChainsMultichain
Tempo MPP Specs is an open-source payment rail by Tempo Labs, Stripe, with last code activity on 2026-10-20 (Active). Latest release on 2026-10-20. Sato Score 63/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →
Check what an install would ask of your keys, before you run it →Last commit Oct 20, 2026 · Last release Oct 20, 2026 (spec-artifacts-ecc5f5ce1af0692ea143a33d8049618a50cd8640) · ★ 95
Listed from paymentauth.org on 2026-07-19. Install: not attempted — no install path on record. Evidence →
Next step
Watch Tempo MPP Specs
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on tempoxyz/mpp-specs before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →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.
Sato Score
63/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 0/10
- Docs & demo
- 0/10
- Listing transparency & provenance
- 7/15
- Independent verification
- 3/10
Evidence — listed vs checked · what the words mean
Listed from paymentauth.org on 2026-07-19. Install: not attempted — no install path on record.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | paymentauth.org | as of 2026-10-21 |
| Verification status | Unverified — not independently reviewed | self-reported | paymentauth.org | as of 2026-10-21 |
| Recent activity | last release 2026-10-20 · last commit 2026-10-20 | observed | github.com/tempoxyz/mpp-specs | 2026-10-21 |
| Website answers | answered (HTTP 200) | observed | paymentauth.org | 2026-10-21 |
| Daily check record | 90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-20 |
| Built by | Tempo Labs, Stripeconfidence 0.80 | self-reported | github.com/tempoxyz/mpp-specs | as of 2026-08-08 |
| Sato Score | 63/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-21 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Observed record — 91 daily checks since 2026-07-23
- Succeeded
- 91
- Failed
- 0
- Their error
- 0
- Unattributed
- 0
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.
Last 30 days — to 2026-10-21, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Measured on-chain — week 2026-W43
What we can observe about this project on-chain, from public reads, with the method and sample size attached to every figure. A raw deployment count is not an adoption figure and is shown separately below.
Rates on fewer than 20 observations are shown but not quotable. Full venue detail: tempo_mpp · The onchain agent economy.
Details
- Chains
- Multichain
- Agent types
- Payment protocol specification
- Open source
- Yes
- Last checked
- 2026-10-21
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.
Where Tempo MPP Specs fits
Related concepts: How Agents Use Wallets, What Are Onchain Agents?
Recent Activity
All news →Releases and posts from Tempo MPP Specs, pulled from its GitHub and X.
mpp-specs Latest spec artifacts
Auto-published spec build artifacts from commit ecc5f5c . Contains HTML, TXT, XML, and PDF renderings of all IETF Payment Auth specifications.
mpp-specs Latest spec artifacts
Auto-published spec build artifacts from commit bba0679 . Contains HTML, TXT, XML, and PDF renderings of all IETF Payment Auth specifications.
mpp-specs Latest spec artifacts
Auto-published spec build artifacts from commit 782abae . Contains HTML, TXT, XML, and PDF renderings of all IETF Payment Auth specifications.
mpp-specs Spec preview for PR #310
Auto-generated spec preview assets for PR #310 .
mpp-specs Latest spec artifacts
Auto-published spec build artifacts from commit 50309c8 . Contains HTML, TXT, XML, and PDF renderings of all IETF Payment Auth specifications.
mpp-specs Latest spec artifacts
Auto-published spec build artifacts from commit 27a274a . Contains HTML, TXT, XML, and PDF renderings of all IETF Payment Auth specifications.
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.
- Oct 20, 2026New release published
- Oct 16, 2026New release published
- Sep 29, 2026Edited: description short, description long
- Sep 26, 2026Edited: entity class, resource type
- Aug 8, 2026Auto-enriched: creator name
- Jul 28, 202626 releases trackedShowing the 2 most recent. Full release history is retained in the listing record.
- Jul 24, 2026Sato Hub began tracking this listing
- Jul 19, 2026Edited: chains supported
- Jul 19, 2026Listed on Sato Hub
Compared with
Related Resources
Agent Payments Protocol (AP2)
ActiveOpen protocol from Google for secure agent-led payments across traditional and crypto rails, with a crypto-native x402 extension built with Coinbase, Ethereum Foundation, and MetaMask.
x402
EarlyOpen HTTP 402 payment protocol, now at the x402 Foundation: agents pay per request in stablecoins, and by a newly merged spec, in bitcoin over Lightning.
PayAI Network
ActiveSolana-first x402 payment facilitator enabling usage-based, machine-to-machine payments for AI agents.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Tempo MPP Specs
- Is Tempo MPP Specs open source?
- Yes. Tempo MPP Specs is open source; the repository is https://github.com/tempoxyz/mpp-specs. Checked as of 2026-10-21.
- Which chains does Tempo MPP Specs support?
- Tempo MPP Specs lists support for Multichain as of 2026-10-21.
- Is Tempo MPP Specs still maintained?
- The most recent code activity Sato Hub observed was on 2026-10-20 (last commit 2026-10-20, last release 2026-10-20), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Tempo MPP Specs?
- Sato Hub has no deploy spec for Tempo MPP Specs; follow the project's own documentation at https://github.com/tempoxyz/mpp-specs.
- Is Tempo MPP Specs verified on Sato Hub?
- No independent verification is on record for Tempo MPP Specs; its verification status is "Unverified" and its Sato Score is 63 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Tempo MPP Specs — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/tempo-mpp-specsData last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.