Agent-native standard
MPP
MPP is the Machine Payments Protocol: pay-per-execution micropayments for the agent economy. KeeperHub is registered on MPP and live since 2026-04-13. The first external agent payment settled on 2026-04-14.
About MPP
MPP (Machine Payments Protocol) was co-authored by Tempo and Stripe to solve the billing problem for agent-initiated workloads. Human-style subscriptions do not fit an economy where agents make many small, autonomous calls. MPP is built for that: granular pricing per execution, settlement on Tempo (and other compatible chains), and client-negotiated protocol selection. It is designed to complement x402 rather than replace it.
KeeperHub's integration
Live since 2026-04-13. KeeperHub is registered on mppscan.com as server ID 3a9395b49a059838086613a280a30d94b812991214d6fcb215a1d3c2196d5785. Dual-protocol with x402: agent clients arriving with either rail can pay and execute.
First external payment verified on 2026-04-14. An AgentCash client parsed the KeeperHub 402 challenge, auto-selected MPP on Tempo based on its wallet's Tempo USDC.e balance, settled $0.01 on-chain (tx 0x89379ee79970bff0f036bd43ca481b9bee5f62e29d5d0596944e54f14cb129c8), and triggered a verified workflow execution (execution ID pnp92qs85y37rgaq328ms).
Why it matters
How agents use MPP with KeeperHub
Micropayments built for the agent economy
Granular per-transaction pricing with no pre-funded account. Ideal for swarms of small agents executing frequent, low-value actions.
Dual-protocol with x402
Agent clients that speak both can auto-select MPP or x402 based on what chain and token their wallet already holds.
Tempo-native settlement
Payments settle on Tempo USDC.e (or other MPP-compatible chains and tokens). Low fees, fast finality.
Auto-discovered via mppscan
Agents crawling mppscan.com find KeeperHub and onboard without human coordination or marketing funnels.
First external payment in production
On 2026-04-14, an AgentCash client (unrelated to KeeperHub code) parsed our challenge, auto-selected MPP on Tempo, settled $0.01 on-chain, and triggered a verified workflow execution.
Pricing aligned to agent workload
Cost scales with executions, not seats. A quiet agent pays nothing. A busy agent pays proportional to its activity.
Getting started
Using MPP with KeeperHub
Call a KeeperHub workflow endpoint
Standard HTTP request from your MPP-capable agent client.
Receive the 402 challenge
KeeperHub returns an MPP payment option (alongside x402) with settlement terms.
Settle on Tempo via your MPP client
The client selects a compatible chain and token based on your wallet state, settles the micropayment on-chain, and retries the request.
Workflow executes
KeeperHub verifies the payment, runs the workflow with managed retries and audit trail, returns the result.
References
Further reading
- mpp.dev - official protocol site
- mppscan.com - ecosystem explorer with KeeperHub registered
- x402 (HTTP payment protocol) - the dual-protocol partner rail
Ship an MPP agent today
Dual-protocol with x402. Your MPP agent hits a KeeperHub endpoint, settles on Tempo, executes.
