# Payment Card Number Validator

> Payment Card Number Validator is a paid API for AI agents from creditcard.openverbs.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-14).

Validates a payment card number by checking its format and authenticity using standard card number verification algorithms.

## Facts

- Endpoint: POST https://creditcard.openverbs.com/v1/validate
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-card-number-validator-195868e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kUMQC2zlxapCHsdIHgACJ

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability payment-card-number-validator-195868e7 -d '<json body>'
```

Example prompt: Can you check whether this credit card number is valid: 4111 1111 1111 1111?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call card number validation without integrating a full payment processor SDK. Ideal for pre-screening card numbers at form entry or before sending to a payment gateway, or for fraud detection pipelines that need to verify card number integrity cheaply. Prefer this over building your own Luhn check when you need a reliable hosted service with no setup overhead.

## Known failure modes

- Missing or empty card number input returns a validation error
- Card number exceeding 40 characters is rejected
- Malformed request body (wrong bodyType or missing required fields) returns a 400 error
- Network timeout or service unavailability returns a 5xx error
- Invalid characters other than digits, spaces, or hyphens may cause parsing errors

## How this service works

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).

## Output

Returns a validation result indicating whether the submitted card number is valid or invalid, typically including format correctness and whether it passes the Luhn algorithm check, and possibly the detected card network (Visa, Mastercard, Amex, etc.).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object",
     "required": [
      "number"
     ],
     "properties": {
      "number": {
       "type": "string",
       "maxLength": 40,
       "minLength": 1,
       "description": "Card number; spaces and hyphens are allowed."
      }
     },
     "additionalProperties": false
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/payment-card-number-validator-195868e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from creditcard.openverbs.com](https://www.zero.xyz/host/creditcard.openverbs.com/llms.txt)