JSON Schema validator
Validate JSON with precise paths and readable errors.
This check runs on the server. Input and results are not saved as execution history; hosted allowances apply.
About JSON Schema validator
Validate a JSON document against JSON Schema draft 7 or 2020-12, with paths and reasons for every reported error.
When to use it
Validate generated API payloads before sending them.
A missing required name → path /, keyword required and a readable reasonHow to use it
- Paste the JSON document and its schema.
- Run validation without modifying the document.
- Use the instance paths to fix missing or incorrectly typed values.
Validate without changing the payload
Paste the document in the main editor and its JSON Schema in the schema field. Select the draft through the schema’s $schema value, or omit it for draft 7. Errors include the instance path, validation keyword and details such as the missing property. Empty error lists mean the supplied document matches that schema.
The validator does not coerce values, remove properties or insert defaults. Common format checks are enabled. Local references are supported, while external references must be bundled first. Pattern validation uses RE2, which intentionally excludes backreferences and lookarounds. Hosted runs use the normal tool allowance and do not retain source documents.
Limits & privacy
64 KiB per document and schema, 64 nesting levels and 100 reported errors. Draft 7 and 2020-12 with common formats. Remote references are never fetched. Patterns use a bounded RE2 engine; unsupported expressions return a schema error. Numbers that would lose precision are rejected. Input and schemas are not retained.
Use this tool from the API reference or connect through the SDK, CLI, SSH, or MCP. Hosted calls share your plan allowances.