# Claude Code Plugin Manifest Change Auditor

> Claude Code Plugin Manifest 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-15).

Audits and validates JSON changes between two Claude Code Plugin Manifest documents, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-claude-code-plugin-manifes-8a081ede-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/claude-code-plugin-manifest-change-auditor-78a22b07
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_e4zHON0gaTfURboadfL4Q

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 claude-code-plugin-manifest-change-auditor-78a22b07 -d '<json body>'
```

Example prompt: Can you audit my Claude Code plugin manifest changes? Here's the before version: {} and the after version: {"name":"my-plugin","version":"1.0","description":"does stuff"} — tell me what paths changed and whether any new schema errors were introduced.

## When to prefer this

Choose this endpoint when you specifically need to validate and diff Claude Code Plugin Manifest JSON documents against the pinned SchemaStore definition, tracking schema compliance across two versions. Prefer it over generic JSON diff tools when you want schema-aware error reporting (not just structural diffing) and need to know whether changes introduced or resolved rule violations.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON provided in before or after fields — parse error returned
- SchemaStore definition unavailable or stale — validation may be incomplete
- Non-JSON formats (YAML, TOML) not supported — will fail silently or error

## How this service works

Change audit: Claude Code Plugin Manifest: Audit JSON changes and validate before/after for Claude Code Plugin Manifest. 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 introduced or resolved relative to the Claude Code Plugin Manifest SchemaStore definition.

## 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/claude-code-plugin-manifest-change-auditor-78a22b07/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)