# Change Audit: lsdlschema.json

> Change Audit: lsdlschema.json 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).

Validates and audits before/after JSON document changes against a pinned lsdlschema.json SchemaStore definition, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-lsdlschema-json-de42bcb1-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-lsdlschema-json-d21e8b8d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rrJm2rmI3SHOam8-6tfk5

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-lsdlschema-json-d21e8b8d -d '<json body>'
```

Example prompt: Can you audit these two JSON documents for me — the before and after versions — and tell me what paths changed and whether any new lsdlschema.json schema violations were introduced or resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the lsdlschema.json SchemaStore schema and want a structured diff of introduced or resolved violations. It is purpose-built for lsdlschema.json compliance auditing of before/after document pairs, not for general JSON diffing, YAML validation, or other schema types.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted (YAML/TOML not supported) — parse error returned
- Network or payment failure — no audit result returned
- Schema definition unavailable or pinned version mismatch — may return incomplete results

## How this service works

Change audit: lsdlschema.json: Audit JSON changes and validate before/after for lsdlschema.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 listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations from the lsdlschema.json SchemaStore definition that were introduced or resolved by the change. Documents are limited to 100 KB and 32 nesting levels each.

## 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-lsdlschema-json-d21e8b8d/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)