# Change Audit: Models CLI JSON Schema Validator

> Change Audit: Models CLI JSON Schema Validator 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-18).

Audits JSON changes between before/after documents for models CLI, reporting added/removed/changed paths and validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-models-cli-538a7639-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-models-cli-json-schema-validator-43167b0d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_csNpYdk2ctGIGIivOUgUY

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-models-cli-json-schema-validator-43167b0d -d '<json body>'
```

Example prompt: Can you audit the change I made to my models CLI JSON config — here's the before version and the after version — and tell me which paths changed, what schema rule violations were introduced or resolved, and whether the updated config is valid?

## When to prefer this

Choose this endpoint when you need to audit specific before/after changes to a models CLI JSON configuration against a pinned SchemaStore definition, particularly when you want to know which JSON paths changed and whether schema errors were introduced or resolved. Prefer this over generic JSON diff tools when you need schema-aware validation tied to the models CLI spec rather than just structural diffing.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON submitted (non-parseable) — validation cannot proceed
- YAML or TOML input submitted instead of JSON — not supported
- Network or payment failure via x402 protocol — no audit returned

## How this service works

Change audit: models CLI: Audit JSON changes and validate before/after for models CLI. 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 of JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations, and lists which validation errors were introduced or resolved in the transition.

## 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-models-cli-json-schema-validator-43167b0d/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)