# Change Audit: POPxf JSON Schema Validator

> Change Audit: POPxf 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-19).

Audits before/after JSON documents for POPxf schema compliance, reporting added/removed/changed paths and introduced/resolved validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-popxf-15fddfd7-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-popxf-json-schema-validator-659c2c2c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QbBVioUqpYdyUjK9YPy_B

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-popxf-json-schema-validator-659c2c2c -d '<json body>'
```

Example prompt: Can you audit these two POPxf JSON configs for me — here's the before version and here's the after version — and tell me what paths changed, any new schema violations that were introduced, and any errors that got resolved?

## When to prefer this

Use this endpoint when you specifically need to validate and diff JSON documents against the POPxf schema definition, particularly when you want to understand both structural changes (added/removed/changed paths) and schema compliance changes (introduced or resolved violations) between two versions of a POPxf configuration. Prefer this over generic JSON diff tools when POPxf-specific schema rule checking is needed.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting depth exceeds 32 levels — rejected with depth error
- Malformed JSON input (non-parseable) — returns parse error
- YAML or TOML input provided instead of JSON — not supported, returns format error
- Payment not completed — request not processed

## How this service works

Change audit: POPxf: Audit JSON changes and validate before/after for POPxf. 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; a list of schema rule violations present in before and/or after documents; newly introduced errors (present in after but not before); and resolved errors (present in before but not after). Based on the pinned SchemaStore definition for POPxf.

## 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-popxf-json-schema-validator-659c2c2c/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)