# Change Audit: petstore-v1.0 JSON Schema Validator

> Change Audit: petstore-v1.0 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 document changes for petstore-v1.0 by comparing before/after documents, reporting added/removed/changed paths and validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-petstore-v1-0-abf0bcfd-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-petstore-v1-0-json-schema-validator-7a2d36ce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ouAkZBIO-KU6FmZQWNbAM

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-petstore-v1-0-json-schema-validator-7a2d36ce -d '<json body>'
```

Example prompt: Can you audit the change I made to my petstore-v1.0 JSON config? Here's the before version and the after version — tell me what paths changed, what was added or removed, and whether any new schema violations were introduced.

## When to prefer this

Choose this endpoint when you need to audit changes specifically to a petstore-v1.0 JSON document against its pinned SchemaStore schema definition. It is ideal for CI/CD change reviews, pre-merge validation, or drift detection on petstore API configs. Prefer it over generic JSON diff tools when schema-aware validation and error attribution (introduced vs resolved) matter for the petstore-v1.0 spec.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- YAML or TOML input provided instead of JSON — not supported
- Malformed JSON in before or after field — parse error returned
- Network or service unavailability — HTTP 5xx error

## How this service works

Change audit: petstore-v1.0: Audit JSON changes and validate before/after for petstore-v1.0. 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 diff report including JSON pointers for all added, removed, and changed paths between the before and after documents, along with a list of validation rule violations, newly introduced errors, and resolved errors — all validated against a pinned petstore-v1.0 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-petstore-v1-0-json-schema-validator-7a2d36ce/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)