# JReleaser JSON Change Auditor

> JReleaser JSON Change Auditor is a paid API for AI agents from market.datapackvibe.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-23).

Audits before/after JSON document pairs for JReleaser configuration changes, reporting added/removed/changed paths, JSON pointer violations, and introduced or resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-jreleaser-e87db8a2-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jreleaser-json-change-auditor-3ae56770
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rKKWStRn9Odh6T8QnDiWF

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability jreleaser-json-change-auditor-3ae56770 -d '<json body>'
```

Example prompt: 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?

## When to prefer this

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.

## Known failure modes

- 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

## How this service works

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.

## Output

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.

## Request schema (JSON Schema)

```json
{
 "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."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/jreleaser-json-change-auditor-3ae56770/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from market.datapackvibe.com](https://www.zero.xyz/host/market.datapackvibe.com/llms.txt)