# Change Audit: epr-manifest.json

> Change Audit: epr-manifest.json 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-14).

Validates and diffs two versions of an epr-manifest.json document, reporting added/removed/changed JSON paths and introduced/resolved schema errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-epr-manifest-json-60c4eb52-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-epr-manifest-json-fcd5496c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PlZRYClj1DOSMzsuSd3ff

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-epr-manifest-json-fcd5496c -d '<json body>'
```

Example prompt: Can you audit the changes I made to my epr-manifest.json? Here's the before version and the after version — I want to know which JSON paths were added, removed, or changed, and whether I introduced or resolved any schema errors.

## When to prefer this

Use this endpoint when you specifically need to audit changes to an epr-manifest.json file with schema validation grounded in the SchemaStore definition for that format. It is ideal for CI pipelines, pre-commit hooks, or developer workflows where you need precise JSON pointer-level change attribution combined with schema compliance checks. Prefer this over generic JSON diff tools when epr-manifest.json schema conformance matters alongside the structural diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (not parseable) — validation cannot proceed
- Malformed request body missing before or after fields — error returned
- Network or payment processing failure — no result returned

## How this service works

Change audit: epr-manifest.json: Audit JSON changes and validate before/after for epr-manifest.json. 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-level diffs between the before and after documents (added, removed, and changed paths), along with schema validation results for each version using a pinned SchemaStore definition for epr-manifest.json — including which rule violations were introduced and which were resolved.

## 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-epr-manifest-json-fcd5496c/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)