# Change Audit: lego.json Schema Validator

> Change Audit: lego.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-14).

Audits JSON changes for lego.json by comparing before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-lego-json-2c0c468e-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-lego-json-schema-validator-2460fab5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_v5S3M5UtC3DxlrOa9nqHd

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-lego-json-schema-validator-2460fab5 -d '<json body>'
```

Example prompt: Can you audit my lego.json change and tell me what paths were added, removed, or modified, and whether any new schema violations were introduced? Here's the before: {} and after: {"agent_market_example": true}.

## When to prefer this

Choose this endpoint when you specifically need to validate changes to a lego.json file against a pinned SchemaStore definition and want a structured diff of JSON pointer paths alongside introduced or resolved schema violations. It is purpose-built for lego.json change auditing rather than general-purpose JSON diffing or schema validation for other file types.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted as before or after — parse error returned
- Schema definition not applicable to submitted content — may produce unexpected results
- YAML or TOML input not supported — only JSON is accepted

## How this service works

Change audit: lego.json: Audit JSON changes and validate before/after for lego.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 audit report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for lego.json. Documents must be under 100 KB and 32 nesting levels deep.

## 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-lego-json-schema-validator-2460fab5/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)