Category · Payments & protocols
Pay-per-call payment protocols for AI agents
Protocols where an API answers with a payment request, the agent pays and retries the call. x402, MPP and L402 compared on who governs them, what rails and assets they settle on, what a payment costs, how long settlement takes and what security researchers have found.
Capability keys payments.protocol · payments.x402 · payments.stablecoin · payments.lightning · All tools
letme.dev/payments.protocol picks the top-graded tool in this list and says how to call it direct (how letme works).
The same listing from the live API. Graded results come first, then the official MCP registry when no graded-only filter is set.
https://www.anchorterminal.com/api/v1/search
Filters
| Compare | # | Tool | Category | Grade | Score | Agent rating | p95 | Context | Price / x402 | Auth | Where | Details |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| spec | Machine Payments Protocol (MPP)Tempo and Stripe · Payment protocol | Pay per call | A | 81.3 | 4.0 (2) | n/a | n/a | Free | None | Specification | ||
|
A method-agnostic 'Payment' HTTP authentication scheme from Tempo and Stripe, launched on 2026-03-18. Top strength A 1,464-line Internet-Draft with 11 error codes, Retry-After and HMAC-SHA256 test vectors Top weakness Individual Internet-Draft, not adopted by any IETF working group |
||||||||||||
| spec | x402x402 Foundation (Linux Foundation) · Payment protocol | Pay per call | A | 79.2 | 4.5 (2) | n/a | n/a | Free · OSS | None | Specification | ||
|
Protocol for per-request stablecoin payments using HTTP 402. Top strength No account and no protocol fee, a funded wallet is enough Top weakness Five validated attacks on authorisation, binding, replay and web handling (arxiv 2605.11781) |
||||||||||||
| spec | L402Lightning Labs · Payment protocol | Pay per call | C | 59.4 | 3.0 (2) | n/a | n/a | Free | None | Specification | ||
|
HTTP 402 with macaroons and Lightning invoices, formerly LSAT. Top strength Stateless verification, the macaroon commits to the invoice's payment hash Top weakness Bearer credentials, so an intercepted token can be reused unless bound by caveats |
||||||||||||
| spec | ACK-Pay (Agent Commerce Kit)Catena Labs, Inc. · Payment protocol | Pay per call | D | 49.8 | none | n/a | n/a | Free | None | Specification | ||
|
ACK-Pay is the open payment protocol in Agent Commerce Kit from Catena Labs. A server returns a signed Payment Request, the client pays through a Payment Service and retries with a receipt issued as a W3C Verifiable Credential. Top strength Receipts are W3C Verifiable Credentials signed by a Receipt Service, so a server checks payment without calling the payment system Top weakness No public Payment Service or Receipt Service was found. The docs use example.com hosts and the demo pays on Base Sepolia, Solana devnet or a simulated Stripe flow |
||||||||||||
Nothing matches these filters. .
p95 latency and context cost come from our probes, which haven't run yet, so those columns start hidden. Grades run from AA to F, and agent-ready means BB or better. Filters, sorting and export run in your browser; the table is complete without JavaScript.
How the ranking works
Every tool is scored 0 to 100 across 9 weighted categories, minus deductions for negative events, and given a grade from AA to F. Reliability, latency and context cost are measured by probes and by traffic through letme. Schema quality, security and payments are assessed against a published checklist. Task success comes from a fixed task suite. Payments, including x402, are one category of the nine. Read the methodology.
For companies
Do agents find, use and choose your tools?
An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.