# Change Audit: Minecraft Data Pack Item Modifier

> Change Audit: Minecraft Data Pack Item Modifier 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 diffs two JSON documents (before/after) against the Minecraft Data Pack Item Modifier schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-item-m-c26f4412-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-minecraft-data-pack-item-modifier-25f95325
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jeJB0dG-noOS2AWjZqiST

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-item-modifier-25f95325 -d '<json body>'
```

Example prompt: Can you audit my Minecraft data pack item modifier JSON — here's the before version and here's the after version — and tell me what paths changed 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 JSON changes for the Minecraft Data Pack Item Modifier schema — it validates both before and after documents simultaneously and highlights what changed between them, making it ideal for CI/CD diff checks, PR reviews, or confirming that manual edits fixed (rather than introduced) errors. Use it over generic JSON diff tools when schema rule compliance matters alongside structural diffing.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: Minecraft Data Pack Item Modifier: Audit JSON changes and validate before/after for Minecraft Data Pack Item Modifier. 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 to added, removed, and changed paths between the before and after documents, along with schema rule violations present in each, newly introduced errors, and errors that were resolved — all evaluated against the pinned Minecraft Data Pack Item Modifier 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-minecraft-data-pack-item-modifier-25f95325/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)