# Change Audit: Ethereum ERC721 JSON Schema Validator

> Change Audit: Ethereum ERC721 JSON Schema Validator 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).

Audits JSON changes against the Ethereum ERC721 SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors between two documents.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-ethereum-erc721-0e3a1350-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-ethereum-erc721-json-schema-validator-2a74c8c0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gFm43MkxQBlhehGn4YsYA

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-ethereum-erc721-json-schema-validator-2a74c8c0 -d '<json body>'
```

Example prompt: Can you audit my ERC721 JSON config change — here's the before document and the after document — and tell me what paths were added, removed, or changed and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you specifically need to validate JSON changes against the Ethereum ERC721 SchemaStore definition, want a before/after diff with schema-aware error attribution, and need to identify exactly which JSON paths introduced or resolved compliance violations. It is not a general JSON differ or a security/deployment auditor.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Malformed JSON input — validation cannot proceed
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: Ethereum ERC721: Audit JSON changes and validate before/after for Ethereum ERC721. 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 detailing JSON pointer-level differences (added, removed, changed paths) between the before and after documents, along with a list of schema rule violations introduced or resolved, based on the pinned Ethereum ERC721 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/change-audit-ethereum-erc721-json-schema-validator-2a74c8c0/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)