# Change Audit: Jsontron (SchemaStore Validation)

> Change Audit: Jsontron (SchemaStore Validation) 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-15).

Validates and diffs two JSON documents (before/after) against the Jsontron schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-jsontron-b6f2acc5-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-jsontron-schemastore-validation-ab4d4d39
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0dH4BjpzXHhqJb9tXybUB

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 change-audit-jsontron-schemastore-validation-ab4d4d39 -d '<json body>'
```

Example prompt: Can you audit my Jsontron config change — here's the before document and the updated after document — and tell me which JSON paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you specifically need to validate JSON changes against the Jsontron schema (via a pinned SchemaStore definition) and want a structured diff of added/removed/changed paths alongside introduced or resolved validation errors. Prefer this over generic JSON diff tools when Jsontron schema compliance is the primary concern.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON input (not valid JSON) — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Payment not included or insufficient (requires 0.01 USDC via x402) — authentication/payment error

## How this service works

Change audit: Jsontron: Audit JSON changes and validate before/after for Jsontron. 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 report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned Jsontron 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/change-audit-jsontron-schemastore-validation-ab4d4d39/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)