# x402.shizu.me Data Validator

> x402.shizu.me Data Validator is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-18).

Validates credit card numbers (Luhn), IBAN bank accounts, email addresses, or arbitrary JSON values against a JSON Schema

## Facts

- Endpoint: POST https://x402.shizu.me/validate?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-shizu-me-data-validator-14bef9a9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6Pxm4_ILkd9ATGLF_OWva

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 x402-shizu-me-data-validator-14bef9a9 -d '<json body>'
```

Example prompt: Can you check if the credit card number 4532015112830366 is valid using a Luhn check?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call validation service in an agent workflow without running local validation libraries. Especially useful for Luhn (credit card), IBAN, and email checks in financial or onboarding flows, or for validating arbitrary JSON payloads against a schema without spinning up a dedicated validator service. The x402 micropayment model makes it ideal for occasional, low-volume checks.

## Known failure modes

- Missing 'type' or 'value' fields in request body returns a 400-level error
- Unsupported type value causes rejection
- For json_schema type, missing 'schema' field causes failure
- Malformed JSON body causes parse error
- Network timeouts on overloaded endpoint

## How this service works

Validate a value. Body: {type, value, schema?}. type = luhn (credit-card number), iban (bank account), email, or json_schema (validate value against a provided JSON Schema). Returns {valid, ...}.

## Output

Returns a JSON object with a 'valid' boolean field indicating whether the supplied value passed the chosen validation. May include additional details depending on the type — for example, error reasons or parsed components of the value.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "type": {},
  "value": {}
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "type": "email",
  "valid": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-shizu-me-data-validator-14bef9a9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)