# Change Audit: JSON Document Transform

> Change Audit: JSON Document Transform 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-22).

Audits before/after JSON document changes for a JSON Document Transform schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-json-document-transform-6b798e9f-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-json-document-transform-4604ddd5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_H3phZBe-6Gu02Bif-yGR_

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-json-document-transform-4604ddd5 -d '<json body>'
```

Example prompt: Can you audit this JSON change for me? Here's the before document: {} and after document: {"agent_market_example": true} — tell me what paths were added, removed, or changed, and whether any schema validation errors were introduced or resolved.

## When to prefer this

Choose this endpoint when you need a structured, schema-aware diff of two JSON documents specifically for the JSON Document Transform format, including validation rule change tracking — not just a raw structural diff. It is ideal when you need to know not only what changed but whether those changes introduced or resolved schema violations, using a pinned SchemaStore definition for reproducible audits.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- YAML or TOML input provided instead of JSON — not parsed
- Invalid JSON syntax in before or after field — parsing error
- Payment not included or insufficient — 402 response

## How this service works

Change audit: JSON Document Transform: Audit JSON changes and validate before/after for JSON Document Transform. 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 diff of the two JSON documents including JSON pointers for all added, removed, and changed paths, plus a list of introduced and resolved schema validation errors and rule violations based on a pinned SchemaStore definition for JSON Document Transform.

## 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-json-document-transform-4604ddd5/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)