{"uid":"cap_4uES0LTp7Vo17KxAfKmbJ","slug":"validate-bundleconfig-json-03f4a383","name":"Validate bundleconfig.json","description":"Validate bundleconfig.json: Validate a JSON document for bundleconfig.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-bundleconfig-json-88a61906-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_UvZPiRXJtF4kXM-skEf0Q","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 bundleconfig.json SchemaStore definition, returning JSON pointer paths and rule violations.","exampleAgentPrompt":"Can you check if my bundleconfig.json is valid? Here's the document: {\"outputFileName\":\"bundle.js\",\"inputFiles\":[\"src/main.ts\"],\"minify\":true} — I want to know if it passes the SchemaStore schema and see any JSON pointer violations.","exampleUseCases":[{"title":"CI pipeline config validation","prompt":"Before I push my build pipeline changes, can you validate this bundleconfig.json against the SchemaStore schema and tell me if there are any rule violations or bad JSON pointer paths? Here's the JSON: {\"outputFileName\":\"dist/app.js\",\"inputFiles\":[\"src/index.ts\"],\"sourceMap\":true}"},{"title":"Debugging broken bundle configuration","prompt":"My bundler is throwing weird errors and I think my bundleconfig.json might be malformed — can you run it through the SchemaStore validator and give me the specific JSON pointer paths where it's failing? The config is: {\"outputFileName\":\"\",\"inputFiles\":null,\"minify\":\"yes\"}"},{"title":"Pre-commit config sanity check","prompt":"I'm about to commit a new bundleconfig.json to the repo — can you quickly validate it against the bundleconfig.json schema and report any violations before I merge? Config is: {\"outputFileName\":\"bundle.min.js\",\"inputFiles\":[\"app.ts\",\"lib.ts\"],\"minify\":true,\"sourceMap\":false}"}],"resultDescription":"A validation report listing JSON pointer paths to violating fields and the specific schema rule violations found in the submitted bundleconfig.json document. If the document is valid, a pass/conformance indicator is returned. Maximum input is 100 KB and 32 nesting levels.","failureModes":["Document exceeds 100 KB limit — request rejected","Nesting depth exceeds 32 levels — validation refused","Input is not valid JSON (parse error before schema validation can begin)","YAML or TOML formats are not supported — must be submitted as JSON","Payment of 0.01 USDC not received — endpoint returns 402","Schema definition unavailable or pinned version mismatch — may return error"],"whenToPreferThis":"Choose this endpoint when you need to validate a bundleconfig.json file specifically against the pinned SchemaStore definition. It is ideal for CI/CD pipelines, pre-commit hooks, or developer tooling workflows where conformance to the official bundleconfig.json schema is required and precise JSON pointer error paths are needed for debugging.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-15T00:50:34.253Z","isFirstParty":false,"canonicalSlug":"validate-bundleconfig-json-03f4a383"}