{"uid":"cap_P4MIBttM83Nhb8ZEglqYg","slug":"validate-dockerd-json-ee3a205b","name":"Validate dockerd.json","description":"Validate dockerd.json: Validate a JSON document for dockerd.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-dockerd-json-47fcfa32-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_HLJFk2OmgxiPvAy-eXfic","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 Docker daemon configuration (dockerd.json), returning JSON pointer violations and rule errors.","exampleAgentPrompt":"Can you validate this dockerd.json config for me and tell me if there are any schema violations or JSON pointer errors? Here's the document: {\"hosts\": [\"tcp://0.0.0.0:2376\"], \"tls\": true, \"log-level\": \"info\"}","exampleUseCases":[{"title":"Pre-deployment Docker daemon config check","prompt":"Before I push this Docker daemon config to production, can you validate this dockerd.json and tell me exactly which fields or values are wrong? Here's the JSON: {\"storage-driver\": \"overlay2\", \"log-driver\": \"json-file\", \"max-concurrent-downloads\": 5}"},{"title":"CI pipeline configuration linting","prompt":"In my CI pipeline I want to automatically check dockerd.json for schema errors — can you validate this document and return all the rule violations with their JSON pointers? {\"insecure-registries\": [\"myregistry.local:5000\"], \"debug\": true}"},{"title":"Troubleshooting invalid Docker daemon config","prompt":"My Docker daemon won't start and I think the config file is malformed — can you run this dockerd.json through the schema validator and tell me what's wrong? {\"experimental\": true, \"metrics-addr\": \"invalid_address\", \"log-opts\": \"should-be-object\"}"}],"resultDescription":"Returns a structured validation report indicating whether the submitted JSON document conforms to the pinned SchemaStore definition for dockerd.json, including a list of JSON pointer paths and associated rule violation messages for any errors found.","failureModes":["Document exceeds 100 KB limit — rejected with size error","JSON nesting exceeds 32 levels — rejected with depth error","Malformed JSON submitted (not parseable) — parse error returned","Empty or null document submitted — may return schema-required field violations","Network or payment processing failure — no validation result returned"],"whenToPreferThis":"Choose this endpoint when you need to validate a Docker daemon configuration file (dockerd.json) against its official SchemaStore definition and receive precise JSON pointer–based error locations. It is ideal for CI/CD pipelines, pre-deployment checks, and debugging daemon startup failures. It is not suitable for YAML/TOML config formats, general JSON validation unrelated to dockerd, or runtime Docker deployment or security auditing.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-29T12:52:42.479Z","isFirstParty":false,"canonicalSlug":"validate-dockerd-json-ee3a205b"}