{"uid":"cap_rKKWStRn9Odh6T8QnDiWF","slug":"jreleaser-json-change-auditor-3ae56770","name":"JReleaser JSON Change Auditor","description":"Change audit: JReleaser: Audit JSON changes and validate before/after for JReleaser. 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-jreleaser-e87db8a2-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_OBIUdNFnIPv56KAp-lVk5","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 for JReleaser configuration changes, reporting added/removed/changed paths, JSON pointer violations, and introduced or resolved schema errors.","exampleAgentPrompt":"Can you audit my JReleaser config changes — here's the before JSON and the after JSON — and tell me which paths were added, removed, or changed, and whether any new schema violations were introduced?","exampleUseCases":[{"title":"Pre-merge JReleaser config review","prompt":"I just updated my jreleaser.json to add a GitHub release distributor. Can you compare the old version and the new version and tell me if any schema rules were violated or if I accidentally removed any required fields?"},{"title":"Catching regressions in release pipeline config","prompt":"My CI pipeline updated the JReleaser config automatically and I want to make sure it didn't break anything. Here's what the file looked like before and after — can you diff them and flag any introduced errors or invalid JSON pointers?"},{"title":"Validating a JReleaser config refactor","prompt":"I refactored our jreleaser.json to reorganize the signing and changelog sections. Please audit the before and after documents against the JReleaser schema and list every path that changed and whether any new violations appeared."}],"resultDescription":"Returns a structured audit report listing JSON pointers for all added, removed, and changed paths between the before and after documents, schema rule violations, and a breakdown of newly introduced errors versus errors that were resolved — all validated against the pinned JReleaser SchemaStore definition.","failureModes":["Document exceeds 100 KB limit — request rejected","JSON nesting exceeds 32 levels — request rejected","Malformed JSON submitted as before or after — parse error returned","YAML or TOML input not supported — must be converted to JSON first","Payment not confirmed — request not processed"],"whenToPreferThis":"Choose this endpoint when you specifically need schema-aware change auditing for JReleaser JSON configuration files with a pinned SchemaStore definition, want structured JSON pointer-level diff output alongside schema violation tracking, and need to distinguish newly introduced errors from pre-existing ones. Prefer it over generic JSON diff tools when JReleaser-specific schema compliance matters.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-23T02:01:51.155Z","isFirstParty":false,"canonicalSlug":"jreleaser-json-change-auditor-3ae56770"}