# Keyronne Payment Card Validator

> Keyronne Payment Card Validator is a paid API for AI agents from keyronne.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Validates payment card numbers via Luhn checksum and detects the card network (Visa, Mastercard, Amex, Discover, etc.) with per-network length rules, returning network name, Luhn result, and last four digits.

## Facts

- Endpoint: POST https://keyronne.com/api/card
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keyronne-payment-card-validator-81c14a1f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rmBxcIVonnMTqlDr48UVl

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 keyronne-payment-card-validator-81c14a1f -d '<json body>'
```

Example prompt: Can you check if the card number 4111 1111 1111 1111 is structurally valid and tell me what network it belongs to?

## When to prefer this

Use this endpoint when you need to structurally validate a payment card number client-side or server-side before submission, detect the card network from the number, or batch-validate up to 50 card numbers at once. Prefer this over manual Luhn implementations when you need network detection alongside checksum validation. Note: this confirms structural validity only, not whether a card account is active or has funds.

## Known failure modes

- Card number fails Luhn check — returns Luhn failure with detected network if determinable
- Unrecognized card prefix — network returned as unknown
- Card length does not match network rules — flagged as invalid length
- Invalid input format (non-numeric after stripping spaces/dashes) — returns parsing error
- Batch exceeds 50 cards — request rejected
- Missing card field in request body — returns validation error

## How this service works

Validate payment card numbers: Luhn checksum plus network detection (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay, Maestro) with per-network length rules. Returns the network, Luhn result, and last four digits. Structure only — never that the card exists or has funds. No card data is stored or logged. POST a JSON body like: {"card":"4111 1111 1111 1111"}

## Output

Returns the detected card network (Visa, Mastercard, Amex, Discover, Diners, JCB, UnionPay, Maestro), the Luhn checksum pass/fail result, and the last four digits of the card. Does not confirm card existence, funds, or active status. No card data is stored.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "card": {
   "type": "string",
   "description": "One card number; spaces and dashes ignored."
  },
  "cards": {
   "type": "array",
   "items": {
    "type": "string"
   },
   "maxItems": 50,
   "description": "Batch of card numbers."
  }
 }
}
```

## More

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