{"uid":"cap_GdCNKUmovQN04NXMilCQR","slug":"change-audit-pgrls-schema-validator-9b9e2a2b","name":"Change Audit: pgrls Schema Validator","description":"Change audit: pgrls: Audit JSON changes and validate before/after for pgrls. 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-pgrls-0df61e87-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_ntM_Cc1Q-7khF18sHeEp7","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 before and after for pgrls schema compliance, reporting added/removed/changed paths and introduced/resolved validation errors using a pinned SchemaStore definition.","exampleAgentPrompt":"I just updated my pgrls config — can you compare the old and new JSON versions and tell me if any new schema violations were introduced, which paths changed, and whether any existing errors were resolved?","exampleUseCases":[{"title":"Pre-deploy pgrls config change review","prompt":"Before I deploy this pgrls config update, compare the current JSON with the new one and tell me exactly which fields changed, any new validation errors introduced, and whether any old errors got fixed."},{"title":"Debugging a broken pgrls configuration","prompt":"My pgrls setup stopped working after an edit — here's the before and after JSON. Can you audit the change and point out which paths were added or removed and any new rule violations that appeared?"},{"title":"Automated pgrls schema compliance check in CI","prompt":"Run a schema compliance audit on these two pgrls JSON snapshots — the before is from last night's build and the after is the new candidate — and list all introduced and resolved errors so I can decide whether to merge."}],"resultDescription":"Returns a structured diff report including JSON pointers for all added, removed, and changed paths between the before and after documents, along with a list of newly introduced validation rule violations and any previously existing errors that were resolved, based on the pinned pgrls SchemaStore definition.","failureModes":["Document exceeds 100 KB limit — request rejected","Nesting depth exceeds 32 levels — request rejected","Input is not valid JSON (e.g. YAML or TOML submitted) — parsing error returned","Payment of 0.01 USDC not provided or fails — 402 response","Empty or missing 'after' field — may return empty diff"],"whenToPreferThis":"Use this endpoint when you specifically need schema-aware change auditing for pgrls JSON documents using the pinned SchemaStore definition. It is ideal for CI/CD pipelines, pre-deploy reviews, or debugging configuration regressions where you need to know not just what changed structurally but whether those changes introduced or resolved schema rule violations. Prefer this over generic JSON diff tools when pgrls schema compliance is the concern.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-19T19:15:03.387Z","isFirstParty":false,"canonicalSlug":"change-audit-pgrls-schema-validator-9b9e2a2b"}