# Minecraft Data Pack Recipe JSON Change Audit

> Minecraft Data Pack Recipe JSON Change Audit 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).

Validates and audits before/after JSON changes for Minecraft Data Pack Recipe files against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-recipe-4df44d0f-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/minecraft-data-pack-recipe-json-change-audit-410e4dbe
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hjlb0Hki2EXRI65mlGW96

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 minecraft-data-pack-recipe-json-change-audit-410e4dbe -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Minecraft data pack recipe JSON? Here's the before version and the after version — tell me what paths changed, what was added or removed, and whether I introduced any new schema violations.

## When to prefer this

Choose this endpoint when you need to audit specific before/after changes to a Minecraft Data Pack Recipe JSON file and want schema-level diff reporting (added/removed/changed paths, introduced/resolved errors) against the SchemaStore definition. Prefer this over generic JSON diff tools when Minecraft-specific schema validation and rule violation reporting is required alongside the structural diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Malformed JSON in before or after field — validation cannot proceed
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: Minecraft Data Pack Recipe: Audit JSON changes and validate before/after for Minecraft Data Pack Recipe. 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

A structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations introduced or resolved by the change, based on a pinned SchemaStore definition for Minecraft Data Pack Recipe.

## 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/minecraft-data-pack-recipe-json-change-audit-410e4dbe/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)