# Change Audit: Claude Code Launch Preview JSON Schema Validator

> Change Audit: Claude Code Launch Preview 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-18).

Audits JSON changes between before/after documents against the Claude Code Launch Preview schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-claude-code-launch-preview-7abb56ad-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-claude-code-launch-preview-json-schema-validator-ad9316a6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_bzWKcLUNiHOWy583hHFH1

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-claude-code-launch-preview-json-schema-validator-ad9316a6 -d '<json body>'
```

Example prompt: Can you audit my Claude Code Launch Preview config change — here's the before: {} and the after: {"agent_market_example":true} — and tell me what paths changed and whether any new schema rule violations were introduced?

## When to prefer this

Choose this endpoint when you need schema-aware diff analysis specifically for Claude Code Launch Preview JSON configurations, particularly when you want to know not just what changed structurally but also which schema rule violations were introduced or resolved. Prefer this over generic JSON diff tools when Claude Code Launch Preview SchemaStore compliance matters.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — parse error returned
- Network or payment failure — no audit result returned
- Schema definition unavailable on server — validation cannot proceed

## How this service works

Change audit: Claude Code Launch Preview: Audit JSON changes and validate before/after for Claude Code Launch Preview. 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 each changed path (added, removed, or modified), along with schema rule violations that were introduced or resolved between the before and after documents, scoped to the pinned Claude Code Launch Preview SchemaStore 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-claude-code-launch-preview-json-schema-validator-ad9316a6/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)