Tempo MPP is the machine payment protocol route in the Agent Economy map. The x402-vs-MPP brief frames it as a machine payment/channel style approach associated with Tempo and Stripe infrastructure.
Agent Economy tracks MPP separately from x402 because the two payment patterns are different: x402 emphasizes HTTP 402 per-resource payments, while MPP points toward machine payment channels and stablecoin micropayments on Tempo.
The current route reports Tempo RPC-indexed events, unique payers, unique payees, event types, and daily rows. This is narrower than Dune-backed x402 coverage and should be interpreted as early Tempo-specific visible activity.
. This route was prerendered with the same `data.json` values used by the dashboard.
How this data is tracked
METHODOLOGY
Tempo MPP data is produced by the local RPC indexer summary and exposed through `tempo-data.json`, then merged into `data.json` for the dashboard.
The route uses `tempoMpp.totalEvents`, `tempoMpp.uniquePayers`, `tempoMpp.uniquePayees`, `tempoMpp.byType`, and `tempoMpp.daily` at build time.
Caveat: the x402-vs-MPP brief treats MPP as earlier and narrower in visible data coverage. This route reports Tempo-specific indexed activity rather than broad market share.
It measures RPC-indexed Machine Payment Protocol events on Tempo. The current build embeds 26,457 total events.
How is MPP different from x402?+
The project brief describes x402 as HTTP 402 per-resource payments and MPP as a machine payment/channel style protocol. Agent Economy keeps their metrics separate.
What are unique payers and payees?+
They are distinct addresses extracted by the Tempo summary script. The current build shows 653 payers and 60 payees.
Why is Tempo MPP coverage narrower than x402?+
The current MPP source is a Tempo RPC indexer rather than multiple public Dune dashboards. The page presents it as early visible activity, not a complete cross-chain market.