Use it if you own the route
- You sell API data, content, or tool output through x402 or MPP.
- You are launching a paid route or changed its payment middleware.
- You want a readable first blocker before asking a wallet to pay.
For the human who owns the paid API
Verify an x402 or MPP endpoint before an Agent pays
Your API can be online and still lose paid calls. One missing or unreadable payment field can stop an Agent before checkout begins—leaving you with fewer purchases and more debugging, not a clean outage alert.
AgentMint Verify by Lasting Design is a free, read-only x402 and MPP endpoint verifier for people who own paid APIs. It requests one public paid route without wallet credentials, signatures, or payment, then reports the first observed blocker before checkout can start and the next concrete fix. Billing is disabled during the public beta.
Verify one paid route1 routeExact public paid-resource URL
1 blockerFirst observed pre-payment issue
1 fixConcrete next action
$0Free beta; billing disabled
01 / Fit
Who should use this—and who should not
This page is for the person accountable for a paid endpoint. Your Agent or CI pipeline can use the REST or MCP interfaces later.
Do not use it as proof of payment
- It is not a wallet, checkout client, facilitator, or settlement verifier.
- It cannot validate a private route, dashboard, homepage, or login-only flow.
- It is not a security audit, identity proof, endorsement, or revenue guarantee.
02 / Evidence
What the read-only request checks
AgentMint reads only public pre-payment evidence. It does not continue into signing, payment, settlement, or delivery.
Body or legacy header challenge
Checks version 1 requirements such as scheme, maximum amount, resource, asset, network, recipient, and timeout.
PAYMENT-REQUIRED evidence
Checks the v2 resource and accepted payment requirements, including amount, CAIP-2 network, asset, recipient, scheme, and timeout.
Payment authentication fields
Checks the public Payment challenge exposed through WWW-Authenticate, including amount and any disclosed asset, network, or recipient.
03 / Output
The fields you get back
Each field answers a business question: can checkout start, what terms were disclosed, and can another Agent discover this exact route?
| Field | What AgentMint observes | Why the API owner cares |
|---|---|---|
| Status | Reachability and observed HTTP status, including 402. | Confirms whether a buyer can reach a payment gate at all. |
| Challenge | Supported x402 v1/v2 or MPP challenge and parse result. | Shows whether an Agent has a payment request it can understand. |
| Price | Observed amount or maximum amount and asset when disclosed. | Exposes missing or ambiguous payment terms before checkout. |
| Recipient | Observed payTo, payee, recipient, or equivalent field. | Shows whether the destination is disclosed in the challenge. |
| Network | Observed network, chain, or CAIP-2 identifier. | Shows whether a compatible client can choose the right rail. |
| Discovery | Whether OpenAPI or /.well-known/x402.json covers the exact route. | Separates “works for direct callers” from “can be found by new Agents.” |
04 / Demo
A deterministic example Trust Card
This fixed example demonstrates the format only. It is not customer evidence and no payment was attempted.
DEMO — NO PAYMENT SENT
Checkout may stop before this API earns the call.
The route is reachable and exposes an x402 challenge, but the recipient is missing from the observed payment terms.
First observed blockerPayment recipient not disclosed
Status402 observed
Protocolx402 v2
PaymentNot attempted
Deterministic product demonstration. Not a live scan, customer result, payment test, settlement proof, or delivery proof.
05 / Boundary
What this result cannot prove
A passing pre-payment check means only that the supported evidence was observable and parseable at scan time.
- No wallet behavior: AgentMint accepts no wallet credentials and creates no signature.
- No payment or settlement: it sends no money and cannot prove that a facilitator or network settles.
- No paid delivery: it cannot prove that the seller returns the promised data, content, or tool output after payment.
- No business guarantee: it does not calculate customers, conversions, revenue saved, or loss prevented.
- No security or identity assurance: a Trust Card is observed protocol evidence, not an audit, certification, endorsement, or seller identity proof.
06 / Sources
Protocol sources
The scope above is tied to current official protocol documentation and the deterministic checks implemented by AgentMint.
x402 documents the 402 response and v2 PAYMENT-REQUIRED payment requirements.
Cloudflare documents MPP’s 402 Payment challenge and credential flow.
Product facts and protocol links last reviewed: .