# Change Audit: deployed-cli JSON Schema Validator

> Change Audit: deployed-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 using a pinned SchemaStore definition for deployed-cli, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-deployed-cli-1f980e02-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-deployed-cli-json-schema-validator-a2c98abc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FCgi_ZMcoIEJwu62zzocL

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-deployed-cli-json-schema-validator-a2c98abc -d '<json body>'
```

Example prompt: Can you audit my deployed-cli config change — here's the before and after JSON — and tell me which paths changed, what schema violations were introduced, and whether any existing errors got resolved?

## When to prefer this

Use this endpoint when you need to validate JSON configuration changes specifically for deployed-cli against a pinned SchemaStore schema definition. It is purpose-built for change auditing (before/after diffing) rather than single-document validation, making it ideal for CI pipelines, PR reviews, or pre-deployment checks where you want to know exactly what changed and whether any schema violations were introduced or resolved. It covers up to 100 KB per document and provides JSON pointer-level granularity.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- YAML or TOML input provided instead of JSON — not parsed or validated
- Malformed JSON that cannot be parsed — validation cannot proceed
- Network or payment processing failure — no result returned

## How this service works

Change audit: deployed-cli: Audit JSON changes and validate before/after for deployed-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 audit report including JSON pointers for all added, removed, and changed paths between the before and after documents, a list of schema rule violations in each document, and which errors were newly introduced or resolved by the change. Documents are validated against a pinned SchemaStore definition for deployed-cli.

## 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-deployed-cli-json-schema-validator-a2c98abc/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)