creditcard.openverbs.com
https://creditcard.openverbs.com/v1/validatePaid verification
How it worksNo sponsored paid call yet.
Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.
Quality grade
How grading works- ✓ Answers a real HTTP 402 challenge
- ✓ Publishes a /.well-known/x402 descriptor
- ✓ Payment address on record
- ✓ Settlement network declared
- ✓ Price declared
x402 readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 65.1/100), which weighs availability, payability and on-chain demand. How the two differ
| Valid payment requirements | 10/10 | Payment requirements carry a payee, a mainnet network and a price. |
| Live 402 challenge | 25/25 | Paid endpoint answers with an HTTP 402 challenge (154 ms). |
| x402 version | n/a | x402 version not observed yet. |
| Signed descriptor | n/a | No x402 standard defines a signed descriptor. |
| Uptime (30 days) | 15/15 | 32/32 probes succeeded over 30 days (100%). |
| Resource declaration | 10/10 | Declares 5 paid resource(s). |
| Verified identity | 5/10 | Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control. |
| Freshness + modern flags | 1/5 | not seen in a source for over 30 days; declares x402. |
| Security declaration | n/a | Payment is the access control for an x402 resource. |
Compared with peers
Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 88 · peer median 78
- Latency
- Faster than 66% of peers
- This listing 154 ms · peer median 205 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
- Freshness + modern flags −4
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days; declares x402.
Paid endpoints
5 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.
https://creditcard.openverbs.com/v1/validate
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).
https://creditcard.openverbs.com/v1/network
Detect the issuing network/brand (Visa, Mastercard, American Express, Discover, Diners Club, JCB, UnionPay, Maestro) from the card's IIN prefix, with the network's valid lengths. Returns `network:null` for an unrecognized prefix.
https://creditcard.openverbs.com/v1/mask
Mask a card number for display, keeping the first six and last four digits (the PCI-permitted maximum) and replacing the rest with a mask character (default `*`).
https://creditcard.openverbs.com/v1/format
Format a card number into the conventional display groups for its network (4-6-5 for Amex, 4-6-4 for 14-digit Diners, otherwise groups of four).
https://creditcard.openverbs.com/v1/generate
Generate a random Luhn-valid TEST card number for the given network (default Visa). For testing only — these are not issued cards and cannot be charged. The response is always flagged `test:true`.
How to call
curl -sS -i -X POST https://creditcard.openverbs.com/v1/validate # expect HTTP 402 Payment Required (about 0.002 USDC/call)
Listed in
Directories this entry was found in.