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

> Change Audit: project-1.0.0-beta8.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-15).

Audits JSON changes between two documents (before/after) against the pinned project-1.0.0-beta8.json SchemaStore definition, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-project-1-0-0-beta8-json-50d2a38c-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-project-1-0-0-beta8-json-schema-validator-dc5ab35f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_C44aFEJEi-itpnuAYPAtu

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-beta8-json-schema-validator-dc5ab35f -d '<json body>'
```

Example prompt: Can you audit the changes I made to my project-1.0.0-beta8.json file? Here's the before version: {} and the after version: {"name":"my-project","version":"1.0.0-beta8","agent_market_example":true} — tell me what paths changed and if any schema rules were violated.

## When to prefer this

Choose this endpoint when you need to specifically validate changes to a project-1.0.0-beta8.json file against its pinned SchemaStore schema definition. It is purpose-built for auditing before/after JSON document pairs and identifying schema compliance deltas, making it more precise than a generic JSON differ or a general-purpose schema validator when working with this specific schema version.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON nesting depth exceeds 32 levels — parsing refused
- Malformed JSON in before or after field — validation cannot proceed
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no audit result returned

## How this service works

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

Returns a structured report of JSON pointer differences between the before and after documents, including added paths, removed paths, changed paths, newly introduced schema rule violations, and resolved errors — validated against the pinned project-1.0.0-beta8.json 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-project-1-0-0-beta8-json-schema-validator-dc5ab35f/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)