{"uid":"cap_f_ecZ5mZ6HpUhbKpWz6yn","slug":"validate-debugsettings-json-dff1a3b0","name":"Validate debugsettings.json","description":"Validate debugsettings.json: Validate a JSON document for debugsettings.json. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.","url":"https://market.datapackvibe.com/x402/assistant-schema-debugsettings-json-4406b9b1-validate?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"document":{"default":{},"description":"JSON value to validate; maximum 100 KB, 32 levels."}}},"responseSchema":null,"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.01","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.01/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.01","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_zXCZCRq9Emz8Ca9SM6ZWz","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.01","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 the pinned SchemaStore schema definition for debugsettings.json, reporting JSON pointer paths and rule violations.","exampleAgentPrompt":"Can you check this debugsettings.json content for me and tell me if it's valid? Here's the JSON: {\"version\":\"0.2.0\",\"configurations\":[{\"type\":\"node\",\"request\":\"launch\",\"name\":\"Launch Program\"}]}","exampleUseCases":[{"title":"Pre-commit debug config check","prompt":"Before I commit this change, validate my debugsettings.json to make sure it conforms to the schema — here's the content: {\"version\":\"0.2.0\",\"configurations\":[{\"type\":\"python\",\"request\":\"attach\",\"port\":5678}]}"},{"title":"CI pipeline config validation","prompt":"In my CI pipeline I need to verify this debugsettings.json is schema-compliant and catch any rule violations before deployment: {\"version\":\"0.2.0\",\"configurations\":[{\"type\":\"node\",\"request\":\"launch\",\"name\":\"Debug Tests\",\"program\":\"${workspaceFolder}/test.js\"}]}"},{"title":"Debugging malformed config file","prompt":"My debug configuration keeps failing to load — can you validate this debugsettings.json and point out exactly which JSON paths are invalid? {\"version\":\"0.2.0\",\"configurations\":[{\"type\":\"go\",\"mode\":\"auto\",\"program\":\"main.go\",\"invalidKey\":true}]}"}],"resultDescription":"Returns a validation result indicating whether the supplied JSON document conforms to the pinned SchemaStore definition for debugsettings.json. On failure, includes JSON pointer paths identifying the location of each violation and a description of the rule that was broken. On success, confirms the document is valid.","failureModes":["Document exceeds 100 KB limit — validation rejected","Nesting depth exceeds 32 levels — validation rejected","Malformed JSON submitted (not parseable) — parse error returned","Schema definition unavailable or stale on server — service error","Input is YAML or TOML instead of JSON — not supported, error returned"],"whenToPreferThis":"Choose this endpoint when you specifically need to validate a debugsettings.json file against its canonical SchemaStore definition. It is purpose-built for this schema rather than being a generic JSON Schema validator, so it provides precise, schema-aware error messages with JSON pointer paths. Prefer it over general-purpose validators when you want guaranteed schema fidelity using a pinned definition, and when the document is under 100 KB.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-14T18:57:22.841Z","isFirstParty":false,"canonicalSlug":"validate-debugsettings-json-dff1a3b0"}