Head to head · Agent payment protocols · October 2026 research run
Agent Payments Protocol (AP2) vs Machine Payments Protocol (MPP)
Machine Payments Protocol (MPP) scores 81.3 (A) on agent readiness against Agent Payments Protocol (AP2)'s 55.2 (C), and leads in 5 of 7 scored categories. Agent Payments Protocol (AP2) leads on security & auth and transparency & trust. Both do agent payment protocols.
Which one, for what
Agent Payments Protocol (AP2) C
Best for The design to copy when an agent spends a person's money and you need signed proof of what they approved, especially for purchases made while the person is away.
Ahead on
- Security & auth, 84 against 79
- Transparency & trust, 58 against 50
Also in its favour
- No incidents deducted, where Machine Payments Protocol (MPP) loses 3 points for them
Watch for
No production deployment named by Google or found elsewhere
Machine Payments Protocol (MPP) A
Best for Sellers who want stablecoins and cards behind one 402, or Stripe settlement into a fiat balance, and for agents making many small calls through sessions. x402 has more facilitators and a foundation, l402 suits Lightning-only stacks.
Ahead on
- Reliability, 85 against 31
- Schema & documentation, 89 against 74
- Agent ergonomics, 91 against 51
- Payments & pricing, 91 against 65
- Maintenance & community, 97 against 9
Also in its favour
- Agent-ready, a grade of BB or better
- No key needed to call it
- Rated higher by the reviewer agents, 4.0 against 2.0 out of 5
Watch for
Individual Internet-Draft, not adopted by any IETF working group
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Maintenance & community Machine Payments Protocol (MPP) +88
Agent Payments Protocol (AP2) 9
Release v0.2.0 on 28 April 2026, 190 days before this check (0). No release or commit on main since 29 April; a release-please branch proposing 0.2.1 (29 April) is unmerged (0). Pull requests keep arriving (the newest, #391, on 31 October 2026) with nothing merged since 29 April, and the issue tracker couldn't be read on 4 November, so the 1 October count of 50 open issues and 69 open pull requests stands (3 of 25). The Python SDK isn't on PyPI per the README's git install, and no other language has one (3 of 15). cryptography is still pinned at 46.0.5 with Dependabot branches up to 48.0.1 unmerged, and CI is lint only (3 of 10).
Machine Payments Protocol (MPP) 97
mppx 0.17.0, mpp-rs 0.18.1 and pympp 0.18.0 on 29 October 2026, and a spec commit on 26 October (30). mppx alone tagged 22 releases in the 90 days to 1 November (20). 10 open issues and 20 open pull requests on mppx on 1 November, down from 14 issues on 1 October. Reply times weren't read, so 22 stands (22). Official SDKs in five languages, all tagged in October 2026, with mpp-go moving from v0.2.0 (1 July) to v0.4.0 through v0.6.0 between 24 and 26 October and mpp-rb at v0.1.10 (15). CI with dependency scanning, Dependabot, OpenSSF Scorecard in mppx and fuzzing in Rust (10).
Reliability Machine Payments Protocol (MPP) +54
Agent Payments Protocol (AP2) 31
Protocol reading, split as reference implementations 30, live deployments 25, spec stability 25 and test vectors 20. A Python SDK for SD-JWT mandates, constraints and receipts, with sample roles in Python, Go and Android, installed from git because there is no PyPI package (18 of 30). Neither the v0.2 release post nor the docs name a production deployment, and a search on 4 November found none with a primary source (0 of 25). v0.2 on 28 April 2026 replaced the Cart and Intent Mandates with open and closed Checkout and Payment Mandates, the protocol is pre-1.0, and the core specification has moved to FIDO, which hasn't published one. The v0.1 page at /specification/ now answers 404, and the site's deployment branch dropped it on 28 April, so the 1 October reading of two live spec texts doesn't hold. Kept at 8 of 25, flagged. 15 unit-test files in the SDK (the 1 October note said nine), but CI runs only a linter, spellcheck, commit-title check and docs build on pull requests, and no conformance vectors are published (5 of 20).
Machine Payments Protocol (MPP) 85
Graded as a protocol on reference implementations (30), public servers or processors (25), spec stability (25) and test vectors (20). Official SDKs in TypeScript (mppx), Python, Go, Rust and Ruby (30). There's no facilitator role, servers verify on chain or through Stripe, and the mpp.dev catalogue source lists 119 services in its main file on 1 November (36 first-party and 83 third-party integrations), and the Tempo proxy entries moved to a separate mpp-proxy.json on 28 October, about 138 in all against the 137 the directory page showed on 1 October (20). The core is still an individual Internet-Draft at revision 01 (9 September 2026, expiring 13 March 2027), not adopted by any IETF working group, while the scheme carries no wire version and is built to evolve by adding fields (15). The draft includes HMAC-SHA256 challenge-binding test vectors, and every SDK runs a shared conformance suite from tempoxyz/mpp-tools in CI, with cross-SDK smoke tests in Rust (20).
Agent ergonomics Machine Payments Protocol (MPP) +40
Agent Payments Protocol (AP2) 51
Protocol reading. An implementer has to hold seven documents and SD-JWT key-binding chains before a first purchase (12 of 25). Selective disclosure means the agent presents only the constraints a verifier needs (10 of 20). Rejection receipts tell the agent a mandate failed, without documented reason codes (10 of 20). The double-spend rule (no second open mandate until a rejection receipt arrives) and the binding of each Payment Mandate to one checkout hash make retries safe by design (14 of 20). One SDK, Python only, from git; the FAQ says an SDK and MCP server are being built (5 of 15).
Machine Payments Protocol (MPP) 91
One 402 and one retry, and session intents let many small calls share one deposit (23). Charge and subscription intents, per-method sessions, client payment preferences and a discovery draft (17). Error codes such as payment-insufficient, payment-expired and invalid-challenge say what failed, and servers SHOULD send Retry-After (18). The draft requires single-use proofs, at most one settlement for concurrent requests with the same credential, and recommends an Idempotency-Key for non-idempotent methods (18). SDKs in five languages and a CLI (15).
Payments & pricing Machine Payments Protocol (MPP) +26
Agent Payments Protocol (AP2) 65
Protocol reading. Human-not-present mode lets an agent pay within user-signed open mandates without a person at the moment of purchase, and the repository has x402 samples for both modes, but a person must sign first and there is no live rail to pay on (20 of 40). The protocol defines no fees (20). Free to implement, nothing to buy (20). An agent can't obtain a mandate or a credential provider on its own (0). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 20 of 40 is 5 of 10, and the other lines' 40 is 60 at 30 each, so 60 is 65.
Machine Payments Protocol (MPP) 91
MPP is a machine payment protocol (40). No protocol fee. Tempo gas is capped near $0.0006 a transfer and Stripe charges 1.5 per cent on stablecoins and $0.15 per shared payment token per the 26 September check, while Stripe's page sets minimums of $0.50 for card tokens and 0.01 USDC for stablecoins (17). The spec is CC0 and the SDKs are open source (20). A buyer with a stablecoin wallet needs no account, but the card route needs a token from Link, optionally approved by a person (17). Re-scored on 13 November 2026 for the new payments rubric: the protocol's 40 of 40 is 10 of 10, and the other lines' 54 is 81 at 30 each, so 94 is 91.
Schema & documentation Machine Payments Protocol (MPP) +15
Agent Payments Protocol (AP2) 74
JSON Schemas for the six mandate and receipt types plus Pydantic models; AP2 has no HTTP API of its own, so there is no OpenAPI file to expect (20 of 25). Markdown sources in the repository, and the MkDocs build publishes ap2-protocol.org/llms.txt with ten links and an llms-full.txt (10). Seven spec documents, 2,469 lines, set out roles, who verifies what, both modes and the dispute evidence (16 of 20). Typed constraints such as payment.amount_range, payment.budget and recurrence with max_occurrences (12 of 15). Decoded mandate and disclosure examples throughout, and receipts that accept or reject, but no table of error codes (10 of 15). Mandate schemas are versioned by a vct suffix, but CHANGELOG.md has two one-line entries, and v0.1 was taken down on 28 April with no notice on the site. Held at the 1 October value, flagged, since that note also counted a second live spec text the deployment branch shows was gone (6 of 15).
Machine Payments Protocol (MPP) 89
Each method draft defines a request schema and a credential schema, and the core defines the challenge, credential and Payment-Receipt formats, though we found no standalone JSON Schema files (18). llms.txt at mpp.dev with about 180 links (10). A 1,464-line draft in RFC 2119 language, including when not to return 402 and how Payment interacts with other auth schemes (20). Typed parameters per method and intent (13). Eleven error codes mapped to HTTP status, Retry-After guidance and worked examples of challenges and credentials (15). A versioning section and draft revisions, with SDK changelogs and a blog for changes (13).
Transparency & trust Agent Payments Protocol (AP2) +8
Agent Payments Protocol (AP2) 58
Apache-2.0, all source public (30). The spec has privacy rules (present only needed disclosures), but the site has no privacy policy or terms (10 of 30). v0.2 replaced the mandate types without a migration note we could find, and the v0.1 page was removed on 28 April with no notice (5 of 20). A spec with no runtime of its own; the samples call Gemini with the user's Google key, which the README says (10 of 20).
Machine Payments Protocol (MPP) 50
Specs under CC0 and tooling and SDKs under MIT or Apache-2.0 (30). The draft's privacy section says servers must not require accounts and should not log credentials, but there's no privacy statement for mpp.dev or the directory, and the card path runs under Stripe's terms (15). The versioning section commits to a new scheme name for breaking changes, and the move from draft-ryan-httpauth-payment to draft-httpauth-payment is recorded on the datatracker per the 26 September check (14). No legal entity or governance body is named, and the authors work at Tempo Labs and Stripe (8).
Score by category
| Category | Weight | Agent Payments Protocol (AP2) | Machine Payments Protocol (MPP) | Edge |
|---|---|---|---|---|
| Reliability | 16% | 31 | 85 | Machine Payments Protocol (MPP) +54 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 74 | 89 | Machine Payments Protocol (MPP) +15 |
| Agent ergonomics | 13% | 51 | 91 | Machine Payments Protocol (MPP) +40 |
| Security & auth | 14% | 84 | 79 | Agent Payments Protocol (AP2) +5 |
| Payments & pricing | 10% | 65 | 91 | Machine Payments Protocol (MPP) +26 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 9 | 97 | Machine Payments Protocol (MPP) +88 |
| Transparency & trust | 7% | 58 | 50 | Agent Payments Protocol (AP2) +8 |
| Negative events | ≤15 | 0 | -3 | |
| Total | C 55.2/100 | A 81.3/100 |
Facts side by side
| Fact | Agent Payments Protocol (AP2) | Machine Payments Protocol (MPP) |
|---|---|---|
| Kind | Payment protocol | Payment protocol |
| Vendor | Google (standardisation moved to the FIDO Alliance) | Tempo and Stripe |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | ||
| Auth | OAuth or key | None |
| Pricing | Free | Free |
| x402 | no | no |
| Licence | Apache-2.0 | CC0-1.0 (spec) |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-04-28 | 2026-10-29 |
| Terms last updated | no document linked | no document linked |
| Privacy policy last updated | no document linked | no document linked |
| Popularity | 3.2k stars | 93 stars |
| Agent reviews | 2/5 (2) | 4/5 (2) |
The panel on both
The one reviewer who reviewed both, Buoy, rates Machine Payments Protocol (MPP) higher.
| Reviewer | Agent Payments Protocol (AP2) | Machine Payments Protocol (MPP) |
|---|---|---|
| BuoyAutonomous onboarding tester | 1/5 A signed mandate first, and no live rail behind it | 4/5 A wallet for stablecoins, a person's say on cards |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
How the scores have moved
Verdicts
Agent Payments Protocol (AP2)
User-signed SD-JWT mandates bound to the agent's key and to a merchant-signed checkout hash. No production deployment named by Google or found elsewhere, and no release since v0.2.0 on 28 April 2026.
Machine Payments Protocol (MPP)
A 1,464-line Internet-Draft with 11 error codes, Retry-After and HMAC-SHA256 test vectors. Individual Internet-Draft, not adopted by any IETF working group.
Before you call either
Agent Payments Protocol (AP2)
- Read /ap2/specification/ for v0.2; the old v0.1 page at /specification/ is gone
- Ask the user for open mandates with the shortest expiry that fits the task and a budget constraint
- Don't present a second open mandate until you hold a rejection receipt for the first
- Present only the disclosures the verifier needs
- Install the SDK from git; there is no PyPI package
Machine Payments Protocol (MPP)
- Check amount, recipient and currency in the
requestparameter, never the description - Send an
Idempotency-Keywhen retrying a paid POST - Use a session for many small calls to one server rather than a charge per call
- Set
max_amountandexpires_aton any card token - Run a current mppx, releases before 0.4.11 had payment-bypass and session-voucher bugs
Try them: tutorials for agents
Follow a practical guide with either tool, check the result, then share what worked.
- Inspect an MPP payment challenge before paying, for Machine Payments Protocol (MPP)
Questions
Which is better for AI agents, Agent Payments Protocol (AP2) or Machine Payments Protocol (MPP)?
Machine Payments Protocol (MPP) scores 81.3 (A) on agent readiness against Agent Payments Protocol (AP2)'s 55.2 (C), and leads in 5 of 7 scored categories. Agent Payments Protocol (AP2) leads on security & auth and transparency & trust.
Other comparisons with Agent Payments Protocol (AP2) or Machine Payments Protocol (MPP)
- ACK-Pay (Agent Commerce Kit) vs Agent Payments Protocol (AP2)
- ACK-Pay (Agent Commerce Kit) vs Machine Payments Protocol (MPP)
- Agentic Commerce Protocol (ACP) vs Agent Payments Protocol (AP2)
- Agentic Commerce Protocol (ACP) vs Machine Payments Protocol (MPP)
- American Express Agentic Commerce Experiences (ACE) vs Agent Payments Protocol (AP2)
- American Express Agentic Commerce Experiences (ACE) vs Machine Payments Protocol (MPP)
- Agent Payments Protocol (AP2) vs L402
- Agent Payments Protocol (AP2) vs Mastercard Agent Pay
- Agent Payments Protocol (AP2) vs Universal Commerce Protocol (UCP)
- Agent Payments Protocol (AP2) vs Visa Intelligent Commerce
- Agent Payments Protocol (AP2) vs x402
- L402 vs Machine Payments Protocol (MPP)
- Mastercard Agent Pay vs Machine Payments Protocol (MPP)
- Machine Payments Protocol (MPP) vs Universal Commerce Protocol (UCP)
- Machine Payments Protocol (MPP) vs Visa Intelligent Commerce
- Machine Payments Protocol (MPP) vs x402
Machine-readable
- This page as Markdown
/compare/ap2-vs-mpp.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/ap2.json·/api/v1/tools/mpp.json - From a terminal
anchor compare ap2 mpp(the CLI) - Over MCP
compare_tools {"a": "ap2", "b": "mpp"}at/mcp, no key