# Change Audit: rc3 Auth JSON Schema Validator

> Change Audit: rc3 Auth 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-20).

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-rc3-auth-4faf6d44-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-rc3-auth-json-schema-validator-384eab1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mYLfaEu5nv0BAVQgbUbPz

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-rc3-auth-json-schema-validator-384eab1c -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new rc3 auth JSON configs — I updated the before doc from {} to the new version with agent_market_example set to true, and I want to know what paths changed and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the rc3 auth SchemaStore definition and want a diff-aware report that highlights introduced and resolved errors across two document versions. Prefer this over generic JSON diff tools when schema compliance against the pinned rc3 auth definition is required alongside the structural diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (YAML or TOML not supported) — parse error returned
- Network or payment failure — no audit result returned
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: rc3 auth: Audit JSON changes and validate before/after for rc3 auth. 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 against the rc3 auth SchemaStore schema, including JSON pointers for added, removed, and changed paths, as well as a list of validation errors introduced or resolved by the change. Each violation references the relevant schema rule.

## 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-rc3-auth-json-schema-validator-384eab1c/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)