# Change Audit: Minecraft Data Pack Predicate

> Change Audit: Minecraft Data Pack Predicate 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).

Validates and diffs before/after JSON documents against the Minecraft Data Pack Predicate schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-predic-ab1306d5-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-minecraft-data-pack-predicate-e2cc962a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5392_83b9sgdXCGgRoStI

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-minecraft-data-pack-predicate-e2cc962a -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Minecraft data pack predicate JSON — here's the before and after — and tell me which paths changed, what validation errors were introduced or resolved, and whether the updated file is valid?

## When to prefer this

Choose this endpoint when you need to audit a specific before/after change to a Minecraft Data Pack Predicate JSON file against a pinned SchemaStore definition. It is purpose-built for this schema type and reports both structural diffs and validation state changes in one call, making it ideal for CI checks, PR reviews, or debugging broken predicates. Not suitable for other Minecraft data pack types, YAML/TOML files, or deployment automation.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (not parseable) — error returned
- YAML or TOML input submitted instead of JSON — not supported
- Schema unavailable or pinned definition mismatch — validation may be incomplete

## How this service works

Change audit: Minecraft Data Pack Predicate: Audit JSON changes and validate before/after for Minecraft Data Pack Predicate. 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 of JSON pointer paths that were added, removed, or changed between the before and after documents, along with a list of schema rule violations present in each version, and which errors were introduced or resolved by the change. Up to 100 KB per document is supported.

## 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-minecraft-data-pack-predicate-e2cc962a/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)