# Change Audit: Minecraft Data Pack Metadata

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-metada-2d113b19-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-metadata-4bf5546a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MqQQ8ZVlwBu0nW-MJpWOk

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-metadata-4bf5546a -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Minecraft data pack metadata? Here's the before: {"pack":{"pack_format":10,"description":"My Pack"}} and after: {"pack":{"pack_format":15,"description":"My Updated Pack","filter":{}}} — tell me what changed and if any schema rules were broken or fixed.

## When to prefer this

Choose this endpoint when you need to validate Minecraft Data Pack Metadata JSON specifically (pack.mcmeta files) and want a before/after change audit that highlights schema violations introduced or resolved by the edit. It uses a pinned SchemaStore definition ensuring consistent, reproducible results. Prefer it over generic JSON diff tools when you need schema-aware validation specific to Minecraft data pack metadata.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON input — parse error returned
- YAML or TOML input not supported — must be JSON
- Payment not included or insufficient — x402 payment required error

## How this service works

Change audit: Minecraft Data Pack Metadata: Audit JSON changes and validate before/after for Minecraft Data Pack Metadata. 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 any schema rule violations introduced or resolved by the change, based on the pinned SchemaStore definition for Minecraft Data Pack Metadata.

## 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-metadata-4bf5546a/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)