- What it does
- Validate a JSON value against a JSON Schema (draft 2020-12) and get every error with its JSON Pointer and keyword location, exact decimals and no remote fetches, with a signed record.
- Who it is for
- Agents and their builders.
- Start in one step
- Ask your agent to call
json_schema_validateat llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it. - What to expect
- Testing: open to try. Free
New to this? Start here.
What it does
JSON Schema Validate is for agents and developers that build or check API payloads, tool inputs, config files or structured model output against a JSON Schema and need every error located, not just the first. Validate a JSON instance against a JSON Schema (draft 2020-12, core and validation vocabularies). Send schema and instance as JSON text. Get back valid or invalid and every error with its JSON Pointer into the instance, the JSON Pointer of the failing keyword in your schema, the keyword and a plain message; a schema that is itself not valid 2020-12 (or has a bad pattern or a $ref outside it) gives verdict schema_error with the reason. Nothing is fetched: $ref works inside the schema only. Limits: schema 12,000 and instance 15,000 characters, 32 levels of nesting. It is one of the developer department tools LLPRO builds for the work agents do across business software (GitHub, Openapi, Postman, Aws). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.
- Who it is for
- Agents and developers that build or check API payloads, tool inputs, config files or structured model output against a JSON Schema and need every error located, not just the first.
- Price
- Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
- Limits
- Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Nothing you send is stored by the tool; no model and no network are used. Does not fetch remote $ref targets (a $ref outside the schema, other than the 2020-12 meta-schemas, is a schema_error) and does not assert format (email, date-time, uri ...) or decode content. Validates draft 2020-12 only: a schema whose $schema names another draft (draft-07, 2019-09, 04) is refused; send it without $schema only if it means the same in 2020-12 (items and $ref behave differently). Pattern syntax is read by Python's regex module with the ECMA-262 meanings named in the rule; rare ECMA-only syntax (\u{...}, \k<name>) is not supported, and a pattern that needs over 0.5 s of matching on one string is refused. Limits: schema 12,000 and instance 15,000 characters, 32 levels of nesting, numbers up to 100 digits and between 1e-400 and 1e400, the whole request 30,000 bytes (characters outside US-ASCII count 6 each), and 100,000 keyword evaluations or 3 seconds of work per call; the first 100 errors are listed. No personal data: the instance is screened for emails, SSN and phone shapes and card numbers, which are refused; JSON numbers are not screened (use made-up values); values are not echoed back except numbers and property names in messages.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "json_schema_validate", "arguments": {"schema": "{\"$defs\": {\"age\": {\"type\": \"integer\", \"minimum\": 0}}, \"type\": \"object\", \"required\": [\"name\", \"age\"], \"properties\": {\"name\": {\"type\": \"string\", \"minLength\": 1}, \"age\": {\"$ref\": \"#/$defs/age\"}, \"tags\": {\"type\": \"array\", \"items\": {\"type\": \"string\"}, \"uniqueItems\": true}}, \"additionalProperties\": false}", "instance": "{\"name\": \"Ada\", \"age\": 36, \"tags\": [\"a\", \"b\"]}"}}}For agents
Tool json_schema_validate on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:nalba23s34qkpqwloc55hudwlq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): ZTqiL5exOPtZVBPFQ0QGPduXnfYysADM9+VgrKN6nlU=
For agents that search MCP registries for JSON Schema, JSON Schema validation, draft 2020-12 tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: Validating JSON is one step of building or calling an API. Tell the Hub the whole job; it routes you to the right signed tools (MCP server.json check, CSV schema check).
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card