Discover / proxy.aproxpay.com

AproxPay

□ No challenge detected

Residential proxy fetch (up to 2MB). Returns HTTP 200 with the target body; read X-Target-Status for the origin status. Billed for the forwarded request, not for a 2xx origin response. For larger responses use /v1/proxy/large; at >17 requests a session pass is cheaper.

Listed price
$0.003
Challenge detected
0 of the last check
Last checked
14 Oct, 18:06 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://proxy.aproxpay.com/v1/proxy
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/proxy.aproxpay.com

Recent checks

14 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.14 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
14 Oct, 18:06 UTCNo challenge detected404312ms

Questions

Did our last probe detect a payment challenge?

No. At our last probe on 14 Oct, 18:06 UTC, we detected no payment challenge.

What price is recorded for AproxPay?

Its listed price is $0.003.

What payment terms does AproxPay advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is AproxPay listed?

In x402 Bazaar. Superstables first indexed it on 14 Oct 2026.

Something wrong on this page? Tell us.