# Validate Any JSON Document

> Validate Any JSON Document is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-15).

Validates a JSON document against a pinned SchemaStore 'Any' schema definition, reporting JSON pointer paths and rule violations

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-any-f861073d-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-any-json-document-3b4a37b4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lS6bEdrp3ucRHJMoPivSH

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 validate-any-json-document-3b4a37b4 -d '<json body>'
```

Example prompt: Can you validate this JSON document for me and tell me exactly where it fails — give me the JSON pointer paths and what rule each one violates?

## When to prefer this

Choose this endpoint when you need quick, low-cost ($0.01 USDC) structural validation of a single JSON document using a pinned SchemaStore definition, and you specifically need JSON pointer paths alongside rule violation details. Best suited for developer tooling, pre-processing checks, or debugging JSON payloads up to 100 KB. Not suitable for YAML/TOML, documents requiring deployment guarantees, or security-sensitive validation scenarios.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — validation refused
- Malformed JSON submitted (not parseable) — parse error returned
- YAML or TOML input submitted instead of JSON — not supported, error returned
- Empty or null document body — may return trivially valid or error depending on schema

## How this service works

Validate Any: Validate a JSON document for Any. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.

## Output

Returns a validation report indicating whether the JSON document is valid, and if not, lists each violation with its JSON pointer path and the specific schema rule that was broken. Up to 100 KB documents and 32 nesting levels are supported.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "document": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/validate-any-json-document-3b4a37b4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)
