# Change Audit: RC3 Request Schema

> Change Audit: RC3 Request Schema 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 before/after documents against a pinned rc3 request SchemaStore definition, reporting added/removed/changed paths and validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-rc3-request-332552f2-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-rc3-request-schema-eb5d4038
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AVho9Reuw2sto5EbiCZBt

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-request-schema-eb5d4038 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new rc3 request JSON documents? Here's the before: {} and after: {"agent_market_example": true} — I need to know what paths changed, what rules were violated, and whether any new errors were introduced.

## When to prefer this

Use this endpoint when you specifically need to validate JSON documents against the rc3 request schema definition and want a detailed change audit (not just a diff) that identifies which modifications introduced or resolved schema violations. Prefer this over generic JSON diff tools when schema compliance reporting against the pinned rc3 request SchemaStore definition is required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON input — parse error returned
- YAML or TOML input not supported — must be valid JSON
- Missing or empty after field — validation cannot proceed

## How this service works

Change audit: rc3 request: Audit JSON changes and validate before/after for rc3 request. 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 added, removed, and changed paths; schema rule violations referencing the pinned rc3 request SchemaStore definition; newly introduced errors; and errors resolved between the before and after documents.

## 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-request-schema-eb5d4038/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)