# Change Audit: Minecraft Data Pack Tag

> Change Audit: Minecraft Data Pack Tag 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 Tag schema, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-tag-a27bc7cd-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-tag-05709739
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ihci6fWTrB2dfOU-txUgz

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-tag-05709739 -d '<json body>'
```

Example prompt: Can you audit my Minecraft data pack tag JSON change? Here's the before: {} and here's the after: {"values":["minecraft:stone","minecraft:dirt"]} — tell me what paths changed and whether any schema rules were violated.

## When to prefer this

Choose this endpoint when you need to audit a specific before/after change to a Minecraft Data Pack Tag JSON file and want schema-level validation tied to the official SchemaStore definition, not just a generic JSON diff. It is particularly useful for mod developers or CI pipelines that need to catch schema regressions between versions of a tag file before deploying changes.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is YAML or TOML instead of JSON — not parsed, may error
- Malformed JSON in before or after field — parse error returned
- Payment not included or insufficient — x402 payment required response

## How this service works

Change audit: Minecraft Data Pack Tag: Audit JSON changes and validate before/after for Minecraft Data Pack Tag. 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 pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, validated against a pinned SchemaStore definition for Minecraft Data Pack Tag. Each document is capped at 100 KB and 32 nesting levels.

## 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-tag-05709739/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)