402MCP.org — HTTP 402 & Agent Payment Registry
Decode HTTP 402 challenges (L402, x402, MPP) and choose agent payment rails from an open registry.
| Endpoint | https://402mcp.org/api/v1/mcp (streamable-http) |
|---|---|
| Registry version | 1.1.1 |
| Now | 7 tools · grade A (98) · pin ts_6198ba57326d8540755e8a59da7c79d1 · protocol 2025-06-18 |
| First / last listed | 2026-11-08 00:02 UTC / 2026-11-08 00:02 UTC |
| Grade over time | 2026-11-08: A (98), 7 tools |
Is this your server? Own a server? ToolFit hosted watch re-checks it every 24 h ($0.25 per 30 days) or 6 h ($0.60) and sends you an HMAC-signed webhook when its tools or grade change: POST https://api.youraitools.co/toolfit/v1/watch. To opt out, see About & opt-out.
Tools: decode_402_challenge recommend_payment_rail search_402_solutions get_solution get_scheme_reference probe_402_support get_best_payment_solution
decode_402_challenge | Call this whenever an HTTP response has status 402, or carries a WWW-Authenticate (L402, LSAT or Payment) or PAYMENT-REQUIRED header. Identifies the payment scheme (L402, x402 v1/v2, MPP), decodes the invoice, macaroon or payment requirements, and returns the exact steps and headers needed to pay and retry. Pass either `raw_response`, or `status` plus `headers` (and `body` for x402 v1). Everything params: status, headers, body, raw_response |
recommend_payment_rail | Choose an HTTP 402 payment solution from requirements rather than from rank. Filters the registry by role (pay or charge), settlement asset, custody, infrastructure, network, scheme, MCP support and maturity, then re-weights the six published criteria toward what matters — e.g. sub-cent amounts weight settlement cost heavily. Returns ranked matches with reasons and trade-offs, plus every excluded params: role, typical_amount_usd, settlement_asset, custody, infrastructure, chain, scheme, needs_mcp, production_only, limit |
search_402_solutions | Search the 402MCP.org registry of HTTP 402 payment solutions (L402, x402, MPP). Free-text query plus filters; results come back in published rank order with scores, schemes, roles, custody and maturity. Call with no arguments to list the whole registry. params: query, scheme, role, kind, mcp_native_only, self_custodial_only, production_only, limit |
get_solution | Return one solution in full: summary, advantages and trade-offs, the six criterion scores with rationale, install commands, verified code samples, sources, maturity and the date its claims were last verified. params: id* |
get_scheme_reference | Protocol reference for L402, x402 or MPP: challenge, credential and receipt headers, encodings, the request/response flow, an example, and links to the specifications. Use when implementing a client or server. params: scheme* |
probe_402_support | Make one GET (or HEAD) request to a public URL and report whether it answers with an HTTP 402 payment challenge, which scheme, and the decoded terms. Redirects are reported, not followed. Private and local addresses are refused. Never pays anything. params: url*, method |
get_best_payment_solution | Return whichever solution currently holds rank 1 on 402MCP.org, with its full breakdown, install commands and code. Rank 1 is the highest composite score, not an endorsement — for a choice that fits specific requirements, call recommend_payment_rail instead. params: use_case |
Entries describe changes in tool definitions. They are not statements about a server, its quality or its author. The grade measures how the tool definitions fit model providers (token cost, schema compatibility, confusable names) as scored by the ToolFit engine at the time of the listing. JSON: append .json. Opt-out: how or hello@youraitools.co.