{"uid":"cap_zRKsXkKLD0AWsVBN3MkiJ","slug":"coinslot-json-schema-validator-92cfc4fc","name":"Coinslot JSON Schema Validator","description":"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 }.","url":"https://coinslot.dev/api/json-schema-validate","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"data":{"description":"Document to validate"},"schema":{"type":"object","description":"JSON Schema (draft-07 core subset)"}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.003","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.003/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.003","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_VmWBFlxJ3UFE4mIBczntV","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.003","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates a JSON document against a JSON Schema (draft-07 core subset) and returns all violations with their paths","exampleAgentPrompt":"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.","exampleUseCases":[{"title":"API input contract enforcement","prompt":"I have an incoming webhook payload and I need to check it against this schema before processing it — the schema requires 'orderId' (string), 'amount' (number, minimum 0), 'currency' (enum: USD, EUR, GBP), and 'items' as a required array. Tell me every field that violates the contract."},{"title":"Config file validation before deployment","prompt":"Before I deploy, validate this config JSON against my schema — it should have 'host' (string), 'port' (integer between 1 and 65535), and 'debug' (boolean), all required, and return any violations with their exact paths."},{"title":"Form submission data quality check","prompt":"A user submitted this registration form data as JSON and I want to catch any errors before saving — my schema requires 'username' (string, pattern alphanumeric), 'age' (integer, minimum 18), and 'role' (enum: admin, editor, viewer). Show me all the violations."}],"resultDescription":"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.","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-09-14T06:39:50.472Z","isFirstParty":false}