# Payment Card Number Formatter

> Payment Card Number Formatter 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-15).

Formats a raw payment card number string (with optional spaces/hyphens) into a standardized format

## Facts

- Endpoint: POST https://creditcard.openverbs.com/v1/format
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/payment-card-number-formatter-7c44fa94
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WKOCRRez1yjcp4Pc_uv3F

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-formatter-7c44fa94 -d '<json body>'
```

Example prompt: Can you format this card number for me — it came in with hyphens and I need it standardized: 4111-1111-1111-1111?

## When to prefer this

Use this endpoint when you need to normalize or standardize payment card number strings that may contain inconsistent spacing or hyphen delimiters — for example, when accepting user input, importing from CSVs, or preparing card numbers for display. Prefer this over manual string manipulation to ensure consistent, standards-compliant formatting.

## Known failure modes

- Card number string is empty or missing — returns validation error
- Card number contains invalid characters beyond digits, spaces, and hyphens — likely error response
- Card number length is out of expected range (1–40 chars enforced by schema)
- Network timeout or service unavailability

## How this service works

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

## Output

Returns a formatted/normalized version of the provided payment card number, with consistent spacing or delimiter style applied to the raw input string.

## 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-formatter-7c44fa94/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)