Discover / creditcard.openverbs.com

Validate a card number

■ Challenge detected

Validate a payment-card number: Luhn check-digit test plus network detection and length check. A syntactically valid number that fails Luhn returns `valid:false` (a 200, not an error).

Listed price
$0.002
Challenge detected
1 of the last check
Median response
244 ms
Last checked
14 Oct, 21:21 UTC
In our index since
14 Oct 2026

Endpoint

curl -i https://creditcard.openverbs.com/v1/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/creditcard.openverbs.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, 21:21 UTCChallenge detected402244ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 14 Oct, 21:21 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 Validate a card number?

Its listed price is $0.002.

What payment terms does Validate a card number 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 Validate a card number listed?

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

Something wrong on this page? Tell us.