{"uid":"cap_H3phZBe-6Gu02Bif-yGR_","slug":"change-audit-json-document-transform-4604ddd5","name":"Change Audit: JSON Document Transform","description":"Change audit: JSON Document Transform: Audit JSON changes and validate before/after for JSON Document Transform. 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-json-document-transform-6b798e9f-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_brdcO29UA8dfIAfnvRDHJ","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 before/after JSON document changes for a JSON Document Transform schema, reporting added/removed/changed paths and introduced/resolved validation errors.","exampleAgentPrompt":"Can you audit this JSON change for me? Here's the before document: {} and after document: {\"agent_market_example\": true} — tell me what paths were added, removed, or changed, and whether any schema validation errors were introduced or resolved.","exampleUseCases":[{"title":"Config change validation before deployment","prompt":"I updated our app config JSON — before it had no fields and now it has a new 'featureFlags' block. Can you audit the before and after documents and tell me if any JSON Document Transform schema rules were violated or if new validation errors were introduced?"},{"title":"Detect breaking field removals in API schema","prompt":"We removed the 'userId' field from our JSON Document Transform output. Can you compare the before and after JSON and report exactly which paths were removed and whether that caused any new rule violations?"},{"title":"Verify a data migration output is schema-compliant","prompt":"After running our data migration, I need to check that the JSON output is still valid. Here's what the document looked like before migration and here's the result — can you audit the changes and tell me if any validation errors appeared or were fixed?"}],"resultDescription":"Returns a structured diff of the two JSON documents including JSON pointers for all added, removed, and changed paths, plus a list of introduced and resolved schema validation errors and rule violations based on a pinned SchemaStore definition for JSON Document Transform.","failureModes":["Document exceeds 100 KB limit — request rejected","Nesting depth exceeds 32 levels — request rejected","YAML or TOML input provided instead of JSON — not parsed","Invalid JSON syntax in before or after field — parsing error","Payment not included or insufficient — 402 response"],"whenToPreferThis":"Choose this endpoint when you need a structured, schema-aware diff of two JSON documents specifically for the JSON Document Transform format, including validation rule change tracking — not just a raw structural diff. It is ideal when you need to know not only what changed but whether those changes introduced or resolved schema violations, using a pinned SchemaStore definition for reproducible audits.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-22T12:47:17.255Z","isFirstParty":false,"canonicalSlug":"change-audit-json-document-transform-4604ddd5"}