{"uid":"cap_C3kXb0YyOEFyHSDouTLHW","slug":"spdx-2-3-json-schema-validator-dae1ffcc","name":"SPDX 2.3 JSON Schema Validator","description":"Machine-payable x402 offers and books: software pays per request in USDC on Base over HTTP 402, with no account or API key.","url":"https://market.561.group/v1/assurance/spdx-2-3/schema-check?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","$schema":"https://json-schema.org/draft/2020-12/schema","required":["input"],"properties":{"input":{"type":"object","required":["type","method","bodyType","body"],"properties":{"body":{"type":"object","description":"Submit the SPDX JSON document itself, up to 32768 UTF-8 request bytes. The seller fixes the exact official SPDX 2.3 JSON Schema; caller-supplied schemas and remote references are not used. Schema violations are paid diagnostic results."},"type":{"type":"string","const":"http"},"method":{"enum":["POST"],"type":"string"},"bodyType":{"enum":["json","form-data","text"],"type":"string"}},"additionalProperties":false},"output":{"type":"object","required":["type"],"properties":{"type":{"type":"string"},"example":{"type":"object","required":["valid","issues"],"properties":{"valid":{"type":"boolean","description":"True means only that the submitted JSON passes the frozen upstream SPDX 2.3 JSON Schema. Automatic JSON shape diagnostics against the exact official SPDX 2.3 draft-07 schema. Find missing required fields, wrong nested types, enum violations and unexpected properties with JSON-pointer paths. Exact historical schema only: it does not enforce all textual SPDX requirements (including version/license values, timestamps or documentNamespace presence), inventory truth, digest validity, cross-reference integrity, CVE absence, signatures or legal compliance. SPDX 2.3.1 and 3.x are not covered. Invalid SBOMs are paid diagnostic results; initial experimental price $0.05. Schema by SPDX Project, CC-BY-3.0, unchanged at SHA256 239208b7ac287b3cf5d9a9af23f9d69863971102a5e1587a27a398b43490b89b. Source and attribution: https://github.com/spdx/spdx-spec/blob/aadf3b0b8dbbabdb4d880b0fc714255fea436ff7/schemas/spdx-schema.json"},"issues":{"type":"array","items":{"type":"object","required":["kind","path","keyword","message"],"properties":{"kind":{"enum":["instance","schema"]},"path":{"type":"string"},"keyword":{"type":"string"},"message":{"type":"string"}}}}}}}}}},"responseSchema":{"type":"json","example":{"valid":true,"issues":[]}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.05","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.05/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.05","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.05","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_Uw8WRoHTzaTkF0P37wRPf","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.05","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Validates an SPDX 2.3 JSON document against the frozen official SPDX 2.3 JSON Schema, returning pass/fail and detailed JSON-pointer diagnostic issues.","exampleAgentPrompt":"Can you check whether my SPDX 2.3 SBOM JSON is valid against the official schema? Here's the document — I need to know if there are any missing required fields, wrong types, or enum violations, with exact JSON-pointer paths for each issue.","exampleUseCases":[{"title":"CI pipeline SBOM compliance gate","prompt":"Before we publish this release, run our SPDX 2.3 SBOM JSON through the official schema validator and tell me if it passes — list every issue with its JSON-pointer path so we can fix them."},{"title":"Debugging a malformed SPDX document","prompt":"I've been generating SPDX 2.3 JSON automatically and something's wrong — can you validate this document against the official SPDX 2.3 schema and show me exactly which fields are missing or have the wrong type?"},{"title":"Third-party SBOM acceptance check","prompt":"A vendor sent us their SPDX 2.3 SBOM — can you validate it against the frozen official schema and tell me if it's structurally correct before we accept it into our system?"}],"resultDescription":"A JSON object with a `valid` boolean (true only if the submitted JSON fully passes the frozen official SPDX 2.3 draft-07 schema) and an `issues` array. Each issue object includes `kind` (instance or schema), `path` (JSON-pointer to the offending location), `keyword` (the violated schema keyword), and `message` (human-readable explanation). An empty `issues` array accompanies a valid result. Schema violations are returned as paid diagnostic results even when the document is invalid.","failureModes":["Malformed JSON body causes a parse error before schema evaluation","Document exceeds 32768 UTF-8 byte limit and is rejected","SPDX 2.3.1 or 3.x documents are not covered and may produce unexpected errors","Textual SPDX requirements (version strings, timestamps, documentNamespace) are not enforced — a structurally valid document may still violate SPDX semantics","Payment failure or insufficient USDC balance results in HTTP 402 with no validation result","Caller-supplied schemas or remote $ref references are ignored; only the frozen upstream schema is used"],"whenToPreferThis":"Choose this endpoint when you need a definitive, reproducible structural check of an SPDX 2.3 JSON document against the exact frozen official schema (SHA256-pinned). It is ideal for CI/CD gates, vendor SBOM acceptance workflows, or automated tooling that needs per-request pay-as-you-go validation with no account setup. Prefer it over general JSON Schema validators when SPDX domain correctness and schema provenance matter. Do not use it for SPDX 2.3.1 or 3.x documents, or when full semantic/legal SPDX compliance (digest validity, license identifiers, CVE absence) is required.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-31T18:36:59.749Z","isFirstParty":false,"canonicalSlug":"spdx-2-3-json-schema-validator-dae1ffcc"}