Services / API · Registry
X Pay
GET https://www.api-xpay.com/x402/quote
Listed in a public agent registry. The name is the registry's label, not ours. Not reviewed by a person. See all 14 endpoints from api-xpay.com.
Checked hourly. Hourly: 100 or more distinct payers in the last 30 days, as reported by the registry.
In the capability tree: Payments and money / Invoicing and billing (primary). Placed by a small AI model choosing from the tree's leaves (placement-ai/1, tree/2) on 2026-10-17. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/1): ✓ says what it does; ✓ its latest check passed; ✓ at least 5 payers in 30 days (registry figure).
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:MIA |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 835 ms |
cloudflare:MIA |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 417 ms |
cloudflare:EWR |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 259 ms |
cloudflare:ATL |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 302 ms |
cloudflare:MIA |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 344 ms |
cloudflare:MIA |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 429 ms |
cloudflare:ATL |
Live, valid x402 payment request HTTP 402 | eip155:8453 | 372 ms |
What this evidence does not show
- A passing probe means the endpoint answered an unpaid request with a valid x402 payment challenge on a mainnet network. It does not show that a paid call succeeds or returns useful results.
- Payer and call counts are the registry's own figures, not our measurements.
- The registry's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page.
Machine-readable: /api/v1/services/cand_6ebafe992bb3b981