AgentPay x402 Facilitator
https://x402-agent-pay.com/payVerify signed x402 payments; treasury-scoped settlement is irreversible.
Paid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
x402 readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here A, 72.8/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 20/25 | Endpoint reachable; its 402 challenge was seen earlier (179 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 32/32 probes succeeded over 30 days (100%). |
| Resource declaration | 8/10 | 9 paid resources; 9 sampled lack a description. |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 5/5 | seen in a source within 7 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Compared with peers
Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 67% of peers
- This listing 84 · peer median 78
- Latency
- Faster than 58% of peers
- This listing 179 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Live 402 challenge −5
— Answer the paid path with a valid 402 challenge.
Now: Endpoint reachable; its 402 challenge was seen earlier (179 ms).
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
- Resource declaration −2
— Declare each paid resource with its input and output schema.
Now: 9 paid resources; 9 sampled lack a description.
Paid endpoints
9 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://x402-agent-pay.com/pay
https://x402-agent-pay.com/escrow
https://x402-agent-pay.com/x402/settle
https://x402-agent-pay.com/x402/verify
https://x402-agent-pay.com/facilitator/heatmap
https://x402-agent-pay.com/facilitator/report
https://x402-agent-pay.com/x402ads/slots
https://x402-agent-pay.com/x402ads/buy
https://x402-agent-pay.com/x402ads/register-slot
How to call
curl -sS -i -X GET https://x402-agent-pay.com/pay # expect HTTP 402 Payment Required (about 0.02 USDC/call)
https://x402-agent-pay.com/facilitator/mcp
Listed in
Directories this entry was found in.