# Paper plugin.yml Schema Change Auditor

> Paper plugin.yml Schema Change Auditor 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-20).

Audits JSON changes between before/after versions of a Paper plugin.yml file, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-paper-paper-plugin-yml-438cf2cc-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/paper-plugin-yml-schema-change-auditor-61fadcb7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pkKnQ2FDIgjQhSfMyRrnY

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 paper-plugin-yml-schema-change-auditor-61fadcb7 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Paper plugin.yml — here's the original config as 'before' and the updated one as 'after' — and tell me what paths changed and whether I introduced any new schema violations?

## When to prefer this

Choose this endpoint when you need to specifically validate changes to a Paper Minecraft plugin.yml configuration against the pinned SchemaStore schema definition, and want a diff-aware report showing both structural changes and schema compliance transitions. Prefer this over generic JSON diff tools when schema rule violation tracking (introduced/resolved errors) is needed alongside path-level change detection.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Input is not valid JSON (YAML/TOML not parsed) — parsing error returned
- Malformed request body missing before or after fields — validation error
- Network or payment processing failure — 402 or 5xx response

## How this service works

Change audit: Paper paper-plugin.yml: Audit JSON changes and validate before/after for Paper paper-plugin.yml. 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 audit report listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with schema rule violations that were introduced or resolved relative to the pinned SchemaStore definition for Paper plugin.yml. Reports are scoped to documents up to 100 KB each.

## 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/paper-plugin-yml-schema-change-auditor-61fadcb7/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)