# Change Audit: LOOBin Schema Validator

> Change Audit: LOOBin 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-18).

Audits JSON changes between a before and after document validated against the LOOBin schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-loobin-15709bbb-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-loobin-schema-validator-bab6c287
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PuoZZdvYteBXAe_FWdTZS

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-loobin-schema-validator-bab6c287 -d '<json body>'
```

Example prompt: Can you audit my LOOBin JSON change — here's the before document and the after document — and tell me what paths were added or removed and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to LOOBin JSON documents against the pinned LOOBin SchemaStore schema definition. It is ideal for CI/CD pipelines or code review workflows where you need a precise diff of JSON pointers alongside schema compliance status for both document versions, at a low per-call cost.

## Known failure modes

- Document exceeds 100 KB limit — returns an error indicating the size constraint
- JSON nesting exceeds 32 levels — rejected with a depth violation error
- Invalid JSON submitted (non-parseable input) — parse error returned
- YAML or TOML content submitted instead of JSON — not supported, error returned
- Missing before or after fields — defaults to empty object for before if omitted

## How this service works

Change audit: LOOBin: Audit JSON changes and validate before/after for LOOBin. 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 containing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any newly introduced schema rule violations and any previously existing errors that were resolved, validated against the pinned LOOBin 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-loobin-schema-validator-bab6c287/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)