# Change Audit for Pre-K JSON Schema (prek)

> Change Audit for Pre-K JSON Schema (prek) 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 a before and after document against a pinned SchemaStore 'prek' definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-prek-299e90de-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-for-pre-k-json-schema-prek-738654f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_unfrBu47qICHpIvaw4bm5

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-for-pre-k-json-schema-prek-738654f2 -d '<json body>'
```

Example prompt: Can you audit the changes I made to this prek JSON config — here's the before version and the after version — and tell me which paths changed, which were added or removed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you need to audit schema-level changes to a prek-typed JSON document specifically, want to see both structural diffs (added/removed/changed paths) and validation diffs (introduced/resolved errors) in one call, and need a pinned SchemaStore definition rather than a user-supplied schema. Not suitable for YAML/TOML documents, files over 100 KB, or schemas other than prek.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing error
- Input is not valid JSON (e.g. YAML or TOML) — not supported, returns error
- Malformed request body — missing before or after fields
- Network or payment processing failure — no audit result returned

## How this service works

Change audit: prek: Audit JSON changes and validate before/after for prek. 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 pointers for all added, removed, and changed paths between the before and after documents, along with newly introduced schema rule violations and any previously existing errors that were resolved, based on the pinned SchemaStore prek 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-for-pre-k-json-schema-prek-738654f2/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)