{"uid":"cap_J9hjkdpF0billFIusHBUu","slug":"bpkg-json-change-audit-c419bd19","name":"bpkg JSON Change Audit","description":"Change audit: bpkg: Audit JSON changes and validate before/after for bpkg. 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-bpkg-1f1a95e8-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_ecxcIFVWXC5zdsRfGA2oX","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 pairs against the bpkg SchemaStore schema, reporting added/removed/changed paths and introduced/resolved validation errors.","exampleAgentPrompt":"Can you audit my bpkg config change — here's the before and after JSON — and tell me which paths were added, removed, or changed, and whether any new schema errors were introduced or old ones resolved?","exampleUseCases":[{"title":"Pre-merge bpkg config validation","prompt":"I'm about to merge a PR that edits our bpkg.json — here's the before and after. Can you run a change audit to see if the new version introduces any schema violations or removes any required fields?"},{"title":"Debugging a broken bpkg package","prompt":"My bpkg package stopped working after I edited the config. Here's the original JSON and the current one — can you diff them and tell me what changed and what new schema errors appeared?"},{"title":"Reviewing automated bpkg config updates","prompt":"Our build tool auto-updated the bpkg JSON. Can you compare the old and new versions and give me a full report of every path that was added, removed, or changed, plus any validation rules that were broken or fixed?"}],"resultDescription":"Returns a structured report including JSON pointer paths for all added, removed, and changed fields between the before and after documents, along with a list of schema rule violations introduced and resolved, referencing the pinned bpkg SchemaStore definition. Each call covers one two-document comparison up to 100 KB per document.","failureModes":["Document exceeds 100 KB limit — request rejected","JSON nesting exceeds 32 levels — request rejected","Input is not valid JSON (YAML/TOML not supported) — parse error returned","Malformed request body — validation error","Payment of 0.01 USDC not fulfilled — 402 response"],"whenToPreferThis":"Use this endpoint when you specifically need to audit changes to bpkg package configuration files against the SchemaStore schema definition, getting both a structural diff (added/removed/changed paths) and schema validation delta (introduced/resolved errors) in a single call. Prefer this over generic JSON diff tools when bpkg-specific schema compliance matters, or over generic schema validators when you need to understand what changed between two versions rather than just whether one version is valid.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-20T00:59:31.275Z","isFirstParty":false,"canonicalSlug":"bpkg-json-change-audit-c419bd19"}