# RC3 Folder JSON Change Audit

> RC3 Folder JSON Change Audit 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 for the rc3 folder schema, reporting added/removed/changed paths and validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-rc3-folder-cb0b3609-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/rc3-folder-json-change-audit-87c91b57
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QCCHkXJDpdtvq-1my90tQ

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 rc3-folder-json-change-audit-87c91b57 -d '<json body>'
```

Example prompt: Can you audit these two JSON documents against the rc3 folder schema and tell me what paths changed, what was added or removed, and whether any new schema violations were introduced? Here's the before: {} and the after: {"agent_market_example": true}.

## When to prefer this

Choose this endpoint when you specifically need to audit a JSON change against the rc3 folder SchemaStore schema, want to know exactly which paths were added, removed, or modified, and need to track whether schema rule violations were introduced or resolved by the change. It is distinct from generic JSON diff tools because it applies pinned schema validation rules. Not suitable for YAML/TOML, documents over 100 KB, or deployment/security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON submitted as before or after — parse error returned
- YAML or TOML input submitted instead of JSON — not supported
- Payment not included or insufficient — x402 payment required error

## How this service works

Change audit: rc3 folder: Audit JSON changes and validate before/after for rc3 folder. 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 including JSON pointers identifying what changed, lists of added, removed, and modified paths between the before and after documents, newly introduced schema validation errors, and previously present errors that were resolved — all evaluated against the pinned SchemaStore definition for the rc3 folder.

## 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/rc3-folder-json-change-audit-87c91b57/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)