# Change Audit: act3 JSON Schema Validator

> Change Audit: act3 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 JSON changes between a before and after document using a pinned SchemaStore definition, reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-act3-02035617-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-act3-json-schema-validator-7fa3fa24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UgFVV80IWvDFRLoxIGG6p

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-act3-json-schema-validator-7fa3fa24 -d '<json body>'
```

Example prompt: Can you audit my JSON config change for act3 schema compliance? Here's the before: {} and the after: {"agent_market_example": true} — tell me what paths changed and if any new schema violations were introduced.

## When to prefer this

Choose this endpoint when you need to validate a before/after JSON change specifically against the act3 SchemaStore definition, with detailed JSON pointer-level diff reporting including introduced and resolved errors. Prefer this over generic JSON diff tools when schema compliance and rule violation tracking matter, and when documents are under 100 KB.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting exceeds 32 levels deep — request rejected
- Invalid JSON submitted (YAML or TOML not supported) — parse error returned
- Malformed request body — validation error
- Payment not included or insufficient — 402 Payment Required

## How this service works

Change audit: act3: Audit JSON changes and validate before/after for act3. 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 listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations, newly introduced errors, and errors that were resolved — all validated against a pinned SchemaStore act3 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-act3-json-schema-validator-7fa3fa24/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)