# Change Audit: RC3 Environment JSON Schema Validator

> Change Audit: RC3 Environment 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-14).

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

## Facts

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

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-environment-json-schema-validator-73655879 -d '<json body>'
```

Example prompt: Can you audit these two JSON configs for me — check the before and after against the rc3 SchemaStore definition and tell me which paths changed, what was added or removed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint when you need to audit structural and schema-level changes between two JSON documents specifically in the rc3 environment context, using a pinned SchemaStore definition. Prefer it over generic JSON diff tools when schema rule validation and violation tracking (introduced/resolved errors) matter, not just structural diffing. Not suitable for YAML/TOML, documents over 100 KB, or deployment/security assurance workflows.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting exceeds 32 levels — validation not performed
- Invalid JSON submitted (non-parseable) — parse error returned
- YAML or TOML input submitted instead of JSON — not supported
- Network or payment processing failure — call not executed

## How this service works

Change audit: rc3 environment: Audit JSON changes and validate before/after for rc3 environment. 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 paths that were added, removed, or changed between the before and after documents, along with any schema rule violations introduced or resolved, based on the pinned SchemaStore rc3 definition. Up to 100 KB per document is supported.

## 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-environment-json-schema-validator-73655879/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)