{"uid":"cap_hEDF5917Wwbuk6tb1tTMO","slug":"x402-utils-json-schema-validator-44de7b84","name":"x402 Utils – JSON Schema Validator","description":"Validate a JSON value against a JSON Schema (draft-07 and 2019-09 keywords, formats such as email, uri, date-time) and list every error with its path. Patterns run on RE2, so a schema cannot stall the check.","url":"https://qcb7fnxsbd7fbhj4.68r.lambda-web.us-east-1.on.aws/v1/json-schema?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"data":{"description":"the JSON value to check"},"schema":{"type":"object","description":"the JSON Schema"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_GouGGxJr_CSQxdeUDi52t","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates a JSON value against a JSON Schema (draft-07/2019-09) and returns a detailed list of all validation errors with their paths, using RE2-safe pattern matching.","exampleAgentPrompt":"Can you check if this JSON object is valid against my JSON Schema and list every error with its path? Here's the data: {\"name\": \"Alice\", \"age\": \"thirty\"} and the schema requires 'name' to be a string and 'age' to be an integer.","exampleUseCases":[{"title":"API request payload pre-flight check","prompt":"Before I send this user registration payload to the backend, validate it against my schema — the schema requires 'email' as a valid email format, 'age' as a number between 18 and 120, and 'username' as a string of 3–20 characters. Here's the payload: {\"email\": \"bob@\", \"age\": 15, \"username\": \"x\"}."},{"title":"Debug failing form submission","prompt":"My form submission is getting rejected and I'm not sure why. Can you run this JSON against my draft-07 schema and list every validation error with the exact field path so I know what to fix? The data is {\"dob\": \"not-a-date\", \"phone\": null} and the schema expects 'dob' to be a date-time and 'phone' to be a string."},{"title":"CI pipeline data contract check","prompt":"I need to validate this config file JSON against our internal JSON Schema to make sure it meets the contract before deployment — the schema uses 2019-09 keywords. Give me every error and the path where it fails so we can block the merge if it's invalid."}],"resultDescription":"Returns a structured result indicating whether the JSON value is valid against the provided schema, and if not, a list of all validation errors each with the JSON path to the failing field and a human-readable error message describing the constraint violation.","failureModes":["Invalid or malformed JSON Schema provided — may return a schema parsing error","Data field missing entirely — validation may fail or return unexpected results","Schema references external $ref URIs — remote refs may not be resolved","Regex patterns in schema that are RE2-incompatible are silently safe but may not behave as expected in other validators","Network timeout on the Lambda endpoint under cold-start conditions","Payment of $0.001 USDC not fulfilled — request rejected with 402 status"],"whenToPreferThis":"Choose this endpoint when you need fast, safe, server-side JSON Schema validation with full error reporting and RE2-safe pattern evaluation — especially useful in agentic pipelines where you need to validate API payloads, config files, or user input against a schema before passing data downstream. Prefer it over client-side validators when you want consistent, sandboxed validation without dependency on a local library, or when your schema uses email, uri, or date-time format keywords that require format validation support.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-29T12:34:38.454Z","isFirstParty":false,"canonicalSlug":"x402-utils-json-schema-validator-44de7b84"}