# Change Audit: pattern.json

> Change Audit: pattern.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-15).

Validates and diffs two JSON documents against the pattern.json SchemaStore schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pattern-json-60280168-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/change-audit-pattern-json-2ce828b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YSz1Df1Qzo-2Ts9n3Zi-i

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-pattern-json-2ce828b0 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my pattern.json — here's the old version and the new version — and tell me which JSON paths changed, any new schema violations introduced, and which errors got fixed?

## When to prefer this

Use this endpoint when you specifically need to audit changes to a pattern.json file against its pinned SchemaStore definition and want a precise diff of JSON paths alongside introduced or resolved validation errors. Prefer this over generic JSON diff tools when SchemaStore-backed rule validation matters for pattern.json.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted in before or after fields — parse error returned
- Schema definition unavailable for pattern.json at time of call — validation skipped or error returned
- YAML or TOML input provided instead of JSON — not supported

## How this service works

Change audit: pattern.json: Audit JSON changes and validate before/after for pattern.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 listing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any SchemaStore rule violations that were introduced or resolved in the transition. Up to 100 KB per document.

## 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-pattern-json-2ce828b0/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)