# JSON Change Audit (Any Schema)

> JSON Change Audit (Any Schema) 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).

Audits JSON changes between a before/after document pair against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-any-f861073d-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/json-change-audit-any-schema-47114377
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kJFk05gxEehqD5oMSTuRi

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 json-change-audit-any-schema-47114377 -d '<json body>'
```

Example prompt: Can you audit the change I made to this JSON config — here's the before and after — and tell me which paths changed and whether the new version introduces any schema validation errors?

## When to prefer this

Choose this endpoint when you need to audit a specific before/after JSON change pair against a schema and get a detailed diff of paths and validation errors — particularly for Any-typed JSON documents where you want to catch regressions or breaking changes. Prefer this over generic JSON diff tools when schema-aware error reporting (introduced vs resolved violations) is needed. Not suitable for YAML/TOML, documents over 100 KB, or security/deployment guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Non-JSON input (YAML, TOML) not supported — parse error
- Malformed JSON in before or after field — validation cannot proceed
- Payment not attached or insufficient — 402 response
- Schema definition unavailable from pinned SchemaStore — audit may be incomplete

## How this service works

Change audit: Any: Audit JSON changes and validate before/after for Any. 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

A structured report listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations introduced or resolved by the change, based on a pinned SchemaStore definition. Limited to documents up to 100 KB and 32 nesting levels each.

## 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/json-change-audit-any-schema-47114377/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)