# JSON Schema Validator (Atlas Draft 2020-12 Profile)

> JSON Schema Validator (Atlas Draft 2020-12 Profile) is a paid API for AI agents from data-tools.use.x402atlas.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-17).

Validates JSON records, invoices, and payloads against the bounded Draft 2020-12 Atlas profile, returning valid/invalid status and deterministic JSON Pointer error locations.

## Facts

- Endpoint: POST https://data-tools.use.x402atlas.com/json-schema-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/json-schema-validator-atlas-draft-2020-12-profile-63e0bbc3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nbAD4Y9sLLRKNO-fTC1Lg

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 json-schema-validator-atlas-draft-2020-12-profile-63e0bbc3 -d '<json body>'
```

Example prompt: Can you validate this JSON invoice payload against my Draft 2020-12 schema and tell me exactly where the errors are using JSON Pointer paths?

## When to prefer this

Choose this endpoint when you need strict, deterministic JSON Schema validation against the bounded Draft 2020-12 Atlas profile with exact number support, Go RE2 pattern matching, and JSON Pointer error reporting. Ideal for invoice validation, API payload checking, and data import verification where reproducible results and no remote schema loading are required. Prefer this over general-purpose validators when your environment requires predictable, sandboxed validation without network calls.

## Known failure modes

- Schema uses unsupported keywords outside the Atlas profile subset — request is rejected with an explanation
- Remote $ref or external schema URIs are referenced — these are never fetched and validation fails
- Input JSON is malformed or unparseable — returns parse error before validation
- RE2-incompatible regex patterns in the schema — rejected as unsupported
- Missing required schema or document fields in the request body — returns 400-style error

## How this service works

JSON Schema validation — validate JSON records, invoices and payloads against the bounded Draft 2020-12 Atlas profile; return valid status and deterministic JSON Pointer errors. This validator subset supports exact numbers and local references with Go RE2 patterns; unsupported schemas are rejected and remote schemas are never loaded.

## Output

Returns a valid/invalid status flag and, when invalid, a deterministic list of JSON Pointer paths indicating exactly which parts of the document failed validation, along with error descriptions. No remote schemas are loaded; unsupported schema keywords are explicitly rejected.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/json-schema-validator-atlas-draft-2020-12-profile-63e0bbc3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data-tools.use.x402atlas.com](https://www.zero.xyz/host/data-tools.use.x402atlas.com/llms.txt)