# Change Audit: Minecraft Data Pack Trim Pattern

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-minecraft-data-pack-trim-p-b74725be-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/change-audit-minecraft-data-pack-trim-pattern-179c30bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_OYFcmqvPQm6r3jRf3i0pw

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-trim-pattern-179c30bc -d '<json body>'
```

Example prompt: Compare my old trim_pattern.json and new trim_pattern.json — here's the before: {"type":"minecraft:wild"} and the after: {"type":"minecraft:coast","asset_id":"minecraft:coast"} — tell me what changed, what paths were added or removed, and whether either version has schema violations against the Minecraft Data Pack Trim Pattern spec.

## When to prefer this

Choose this endpoint when you need to validate Minecraft Data Pack Trim Pattern JSON specifically, especially when comparing two versions of a file to understand what changed and whether changes introduced or resolved schema violations. It is purpose-built for this niche schema and provides diff-aware reporting rather than just static validation. Prefer it over generic JSON validators when you need schema-aware change auditing tied to the Minecraft trim pattern spec.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON input (not parseable) — validation cannot proceed
- YAML or TOML input provided instead of JSON — not supported
- Schema definition unavailable or pinned version outdated — may produce incomplete results
- Payment of 0.01 USDC not completed — endpoint returns 402

## How this service works

Change audit: Minecraft Data Pack Trim Pattern: Audit JSON changes and validate before/after for Minecraft Data Pack Trim Pattern. 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 any schema rule violations present in either version, newly introduced errors in the after document, and errors resolved compared to the before document. The response is grounded in a pinned SchemaStore definition for Minecraft Data Pack Trim Pattern.

## 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-trim-pattern-179c30bc/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)