# Change Audit: clib JSON Schema Validator

> Change Audit: clib 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-15).

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-clib-95cb1dd6-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-clib-json-schema-validator-0a4d205d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k8MlgvM5ReNmmxv52Vbhu

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-clib-json-schema-validator-0a4d205d -d '<json body>'
```

Example prompt: Can you audit the changes between my old clib JSON config and the updated one? Here's the before: {} and the after: {"name":"mylib","version":"1.0.0"} — tell me what paths changed and whether any schema violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you specifically need to validate clib JSON documents against the pinned SchemaStore definition and get a structured change audit report. It is ideal for CI/CD pre-merge checks, configuration review workflows, or any scenario where you need to understand both structural diffs and schema compliance changes between two versions of a clib JSON file. Not suitable for YAML/TOML, non-clib schemas, or documents larger than 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation aborted
- Invalid JSON input (non-parseable) — parsing error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: clib: Audit JSON changes and validate before/after for clib. 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 differences between the before and after documents, including paths that were added, removed, or changed, as well as schema rule violations that were introduced or resolved relative to the pinned clib 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-clib-json-schema-validator-0a4d205d/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)