# Change Audit: project-1.0.0-rc1.json Schema Validator

> Change Audit: project-1.0.0-rc1.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 pinned project-1.0.0-rc1.json SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-project-1-0-0-rc1-json-97aac846-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-project-1-0-0-rc1-json-schema-validator-aa070d7f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ueWTlz10cv_a186rXZciJ

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-project-1-0-0-rc1-json-schema-validator-aa070d7f -d '<json body>'
```

Example prompt: Can you audit what changed between these two versions of my project config JSON? Here's the before: {} and after: {"name":"my-project","version":"1.0.0-rc1"} — I want to know which paths changed and whether any new schema violations were introduced according to the project-1.0.0-rc1.json SchemaStore definition.

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the project-1.0.0-rc1.json SchemaStore definition, comparing a before and after state to surface exactly which paths changed and which schema rules were newly violated or resolved. Ideal for CI/CD pipelines, pre-merge config reviews, or any workflow where diff-aware schema compliance matters for the project-1.0.0-rc1 spec.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation fails
- Invalid JSON syntax in before or after input — parse error returned
- YAML or TOML input provided — not supported, only JSON accepted
- Network or service unavailability — no response

## How this service works

Change audit: project-1.0.0-rc1.json: Audit JSON changes and validate before/after for project-1.0.0-rc1.json. 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

A structured report listing JSON pointers for all added, removed, and changed paths between the before and after documents, plus any schema rule violations introduced or resolved according to the pinned project-1.0.0-rc1.json SchemaStore definition. Covers documents up to 100 KB and up to 32 nesting levels.

## 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-project-1-0-0-rc1-json-schema-validator-aa070d7f/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)