{"uid":"cap_DAEEGVkThMglP7RX7v2-a","slug":"change-audit-pdm-json-schema-validator-c35d06e6","name":"Change Audit: PDM (JSON Schema Validator)","description":"Change audit: PDM: Audit JSON changes and validate before/after for PDM. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations, added/removed/changed paths and introduced/resolved errors. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one two-document change audit.","url":"https://market.datapackvibe.com/x402/assistant-schema-pdm-e08b9e8f-changes?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"after":{"default":{"agent_market_example":true},"description":"JSON value to validate; maximum 100 KB, 32 levels."},"before":{"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_n9NVxKD6fRBUZs8NOW9oR","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":"Audits JSON changes for PDM by comparing before/after documents, reporting added/removed/changed paths and introduced/resolved schema violations using a pinned SchemaStore definition.","exampleAgentPrompt":"Can you audit my PDM config change — here's the before JSON and the after JSON — and tell me which fields were added, removed, or changed, and whether any new schema violations were introduced or old ones got fixed?","exampleUseCases":[{"title":"Pre-deploy PDM config review","prompt":"I'm about to update our PDM config file. Here's the old version and the new version — can you run a change audit to show me what paths changed and whether any schema rules are now violated that weren't before?"},{"title":"Debugging a PDM schema regression","prompt":"Something broke in our PDM setup after a config edit. Can you compare this before and after JSON and tell me exactly which fields changed and what new validation errors were introduced?"},{"title":"Verifying a PDM config fix","prompt":"I think I fixed the PDM schema violations in our config. Can you compare the broken version and the updated version and confirm which errors were resolved and whether any new ones were introduced?"}],"resultDescription":"Returns a structured report including JSON pointers to all added, removed, and changed paths between the before and after documents, along with a list of schema rule violations introduced by the change and any violations that were resolved, all validated against a pinned PDM SchemaStore definition.","failureModes":["Document exceeds 100 KB limit — rejected with size error","JSON nesting exceeds 32 levels — rejected with depth error","Malformed JSON input — parse error returned","YAML or TOML input not supported — must convert to JSON first","Payment not included or insufficient — x402 payment required error"],"whenToPreferThis":"Use this endpoint when you specifically need to audit JSON changes for PDM configurations against a pinned SchemaStore definition, tracking exactly which paths changed and whether schema compliance improved or regressed. Prefer this over generic JSON diff tools when PDM schema rule enforcement and before/after violation tracking are required.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-19T19:12:43.659Z","isFirstParty":false,"canonicalSlug":"change-audit-pdm-json-schema-validator-c35d06e6"}