# LSD Config Change Auditor

> LSD Config Change Auditor 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 between a before and after document for lsd config, reporting added/removed/changed paths and schema violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-lsd-config-6b8edefa-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/lsd-config-change-auditor-2438fdc0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f-TqtfeJobiRMO9ythrye

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 lsd-config-change-auditor-2438fdc0 -d '<json body>'
```

Example prompt: Can you audit the change I made to my lsd config? Here's the before: {} and after: {"theme":"dark","font_size":14} — tell me what paths were added, removed, or changed, and whether any schema rules were violated or resolved.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to an lsd config JSON document against its pinned SchemaStore definition. It is purpose-built for lsd config schema validation with diff reporting, making it more precise than a generic JSON diff tool or a general-purpose schema validator. Prefer this when you need both structural change detection (added/removed/changed paths) and schema rule violation reporting in a single call.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON in before or after fields — parse error returned
- No differences detected between before and after — empty change report
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: lsd config: Audit JSON changes and validate before/after for lsd config. 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 including JSON pointers identifying added, removed, and changed paths between the before and after documents, along with a list of introduced schema rule violations and any previously existing errors that were resolved by the update.

## 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/lsd-config-change-auditor-2438fdc0/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)