X Pay
Paid API · www.api-xpay.com · found in a public registry · checked since 2026-10-16
Overdue · latest check
GET https://www.api-xpay.com/x402/status$0.005 per call · from the registry's payment termsThe name is the registry's label, not ours. Not reviewed by a person. See 14 endpoints from api-xpay.com.
Our checks
An unpaid request hourly, from eastern North AmericaLast 30 checks, oldest to newest
30 passed, 0 failed, 0 not run.
Checked hourly. Hourly: 100 or more distinct payers in the last 30 days, as reported by the registry.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hours | 22 | 0 | 259 | — | — | — | 229 | 365 |
| 7 dayssince 2026-10-17 | 45 | 0 | 261 | — | — | — | 229 | 403 |
| 30 dayssince 2026-10-17 | 45 | 0 | 261 | — | — | — | 229 | 403 |
Milliseconds, from eastern North America, timing an unpaid request answered with a payment request (HTTP 402). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Payment terms
- Price per call
- $0.005
- Protocols
- x402
- Networks
- eip155:8453
- Terms changes, 90 days
- 0 in 3 days tracked
Price from the registry's payment terms; protocols and networks from its payment request at our checks. Current terms first seen 2026-10-17; 0 receiving-address changes. Definitions
Reported by the registry
- Payers, 30 days
- 187
- Paid calls, 30 days
- 6371
The registry's own figures, not our measurements.
Access
- Our latest check
- Asked for payment (x402)
- Stated
- not stated
- Payment model
- Per call (asked for payment for our request)
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Listing
In the capability tree: Web access and automation / Website analysis / Uptime and service status (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-19. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/5): ✓ says what it does; ✓ its latest check passed; ✓ at least 5 payers in 30 days (registry figure).
Purpose tags: statushealthopsavailabilityservice
Recent probes
| When | Result | Networks offered | Time to headers |
|---|---|---|---|
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 245 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 244 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 365 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 253 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 261 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 284 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 251 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 255 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 282 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 245 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 262 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 265 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 338 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 347 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 337 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 261 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 229 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 344 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 254 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 257 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 248 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 259 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 248 ms |
cloudflare:MIA |
Live, valid payment request HTTP 402 | eip155:8453 | 403 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 343 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 261 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 235 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 250 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 283 ms |
cloudflare:EWR |
Live, valid payment request HTTP 402 | eip155:8453 | 263 ms |
What these figures do not show
- A passing probe means the endpoint answered an unpaid request with a valid payment request on a production network (x402 on a mainnet network, or MPP on Tempo mainnet). 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 3 days (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_e92a37d9620f0b6b