# Coinslot JSON Schema Validator

> Coinslot JSON Schema Validator is a paid API for AI agents from coinslot.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Validates a JSON document against a JSON Schema (draft-07 core subset) and returns all violations with their paths

## Facts

- Endpoint: POST https://coinslot.dev/api/json-schema-validate
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coinslot-json-schema-validator-92cfc4fc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zRKsXkKLD0AWsVBN3MkiJ

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 coinslot-json-schema-validator-92cfc4fc -d '<json body>'
```

Example prompt: Check whether this user profile JSON conforms to my schema — the schema requires 'name' (string), 'age' (integer, minimum 0), and 'email' (string, pattern matching email format), with 'name' and 'email' as required fields, and tell me every violation with its path.

## When to prefer this

Choose this endpoint when you need server-side JSON Schema draft-07 validation with complete violation reporting including field paths, especially for enforcing data contracts on API payloads, config files, or user-submitted data. It covers types, required, enums, ranges, patterns, nesting, and anyOf/allOf/oneOf — making it suitable for complex schemas. Prefer this over client-side validation when you need an auditable, language-agnostic validation step in an automated pipeline.

## Known failure modes

- Invalid or malformed JSON Schema provided — returns a schema parse error
- Data field missing from request body — returns a bad request error
- Schema uses unsupported draft-07 features beyond the core subset — may silently skip unsupported keywords
- Very deeply nested schemas may hit processing limits
- Non-object schema at top level may behave unexpectedly

## How this service works

Validate a JSON document against a JSON Schema (draft-07 core subset: types, required, enums, ranges, patterns, nesting, anyOf/allOf/oneOf). Returns all violations with paths. POST { schema, data }.

## Output

Returns a list of all schema violations found in the document, each including the JSON path to the offending field and a description of the constraint that was broken. If the document is fully valid, returns an empty violations array.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "description": "Document to validate"
  },
  "schema": {
   "type": "object",
   "description": "JSON Schema (draft-07 core subset)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coinslot-json-schema-validator-92cfc4fc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from coinslot.dev](https://www.zero.xyz/host/coinslot.dev/llms.txt)