Discover / x402-qr-api.vercel.app

x402-qr-api.vercel.app

■ Challenge detected

Validate an email address: format check plus a live MX record lookup on its domain

x402
Base
USDC

Challenge detected: 1 of the last check
Median response: 100 ms
Last checked: 3 Oct, 17:05 UTC
In our index since: 3 Oct 2026

Endpoint

curl -i https://x402-qr-api.vercel.app/api/validate
# 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/x402-qr-api.vercel.app

Recent checks

3 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.3 Oct 2026

All 1 checks

When (UTC)	Result	HTTP	Response
3 Oct, 17:05 UTC	Challenge detected	402	100ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 3 Oct, 17:05 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does x402-qr-api.vercel.app 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 x402-qr-api.vercel.app listed?

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

Something wrong on this page? Tell us.