# Minecraft Data Pack Damage Type JSON Change Audit

> Minecraft Data Pack Damage Type 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-19).

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-damage-d7f2a62c-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/minecraft-data-pack-damage-type-json-change-audit-2cfbed7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vVDsed3rDxGNZsHy1V-u5

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-damage-type-json-change-audit-2cfbed7d -d '<json body>'
```

Example prompt: Can you audit my Minecraft Data Pack Damage Type JSON change — here's the before version and the after version — and tell me which paths were added, removed, or changed, and whether any new schema violations were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you need to validate Minecraft Data Pack Damage Type JSON specifically against the pinned SchemaStore definition and want a structured diff of schema violations and path changes between two document versions. It is purpose-built for Minecraft data pack damage type JSON and not suitable for other Minecraft data pack types or general-purpose JSON diffing.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — validation skipped
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment failure — no audit result returned

## How this service works

Change audit: Minecraft Data Pack Damage Type: Audit JSON changes and validate before/after for Minecraft Data Pack Damage Type. 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 SchemaStore rule violations present in each, newly introduced errors, and errors that were resolved by the change.

## 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-damage-type-json-change-audit-2cfbed7d/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)