# Data Validation (IBAN, ISBN, ISIN & Identifier Checksum)

> Data Validation (IBAN, ISBN, ISIN & Identifier Checksum) is a paid API for AI agents from api.edifiedlab.com, paid per call via x402, $0.211/call, status unknown (last checked 2026-10-02).

Validates structured identifiers — IBAN, ISBN, ISIN, IMEI, VATIN, EAN, LEI, and more — by format and checksum rules, without live external verification.

## Facts

- Endpoint: POST https://api.edifiedlab.com/v1/tools/validate?utm_source=zero.xyz
- Price: $0.211/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/data-validation-iban-isbn-isin-identifier-checksum-a37091b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9L1NOJ3h3aUEm1Sfarlmg

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 data-validation-iban-isbn-isin-identifier-checksum-a37091b0 -d '<json body>'
```

Example prompt: Can you check whether this IBAN is valid — DE89370400440532013000 — and confirm it passes the checksum?

## When to prefer this

Choose this endpoint when you need fast, offline-style format and checksum validation for structured identifiers like IBAN, ISBN, ISIN, IMEI, VATIN, EAN barcodes, LEI codes, or ISSN — particularly when you don't need live registry lookups or real-world existence confirmation. Ideal for data-quality pipelines, form validation workflows, and pre-submission checks where speed and cost matter more than authoritative verification.

## Known failure modes

- Unsupported scheme value returns an error or unrecognized-scheme response
- Malformed input (wrong type for value) may return a 400-level error
- Validation only covers format and checksum — a structurally valid IBAN may not exist in any real bank
- Phone validation may be region-sensitive and produce false negatives without a region param
- JSON schema validation result depends on correctness of the supplied schema object

## How this service works

Validate IBAN, ISBN, and similar identifiers by format and checksum (not real-world verification).

## Output

Returns a validation result indicating whether the identifier conforms to the expected format and passes its checksum algorithm. Typically includes a pass/fail status and, on failure, details about which aspect of validation failed (e.g. invalid check digit, wrong length, unsupported prefix). Does not confirm real-world existence or live registry status.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "type": {
   "enum": [
    "jsonschema",
    "identifier",
    "phone"
   ],
   "type": "string",
   "example": "identifier"
  },
  "value": {
   "type": "string",
   "example": "9780306406157"
  },
  "region": {
   "type": "string",
   "example": "US"
  },
  "schema": {
   "type": "object"
  },
  "scheme": {
   "enum": [
    "bic",
    "ean",
    "ean13",
    "ean14",
    "ean8",
    "gs1_128",
    "iban",
    "imei",
    "imsi",
    "isbn",
    "isbn10",
    "isbn13",
    "isin",
    "ismn",
    "isni",
    "issn",
    "lei",
    "mac",
    "meid",
    "vatin"
   ],
   "type": "string",
   "example": "isbn13"
  },
  "document": {}
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/data-validation-iban-isbn-isin-identifier-checksum-a37091b0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.edifiedlab.com](https://www.zero.xyz/host/api.edifiedlab.com/llms.txt)