Discover / tokencheck.402api.dev

tokencheck.402api.dev

■ Challenge detected

Call before paying an unfamiliar x402 endpoint, or to pick between providers. $0.02, usually <1 s plus one probe: live unpaid probe (status, latency, TLS, PAYMENT-REQUIRED decoded and sanity-checked), seller reputation from indexed on-chain USDC payments to its Base payTo (24 h/7 d count, distinct payers, total and median USD, top-payer share), Bazaar listing and price, and a looks legit/caution/avoid verdict citing each fact. Errors: 400/503 JSON {error}, not charged.

Listed price
$0.02
Challenge detected
1 of the last check
Median response
354 ms
Last checked
10 Oct, 12:22 UTC
In our index since
10 Oct 2026

Endpoint

curl -i https://tokencheck.402api.dev/v1/seller-check
# 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/tokencheck.402api.dev

Recent checks

10 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.10 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
10 Oct, 12:22 UTCChallenge detected402354ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 10 Oct, 12:22 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 price is recorded for tokencheck.402api.dev?

Its listed price is $0.02.

What payment terms does tokencheck.402api.dev 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 tokencheck.402api.dev listed?

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

Something wrong on this page? Tell us.