# AutoAPICase JSON Change Audit

> AutoAPICase JSON Change Audit 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-18).

Audits JSON document changes between before/after versions using a pinned AutoAPICase SchemaStore definition, reporting added/removed/changed paths and introduced/resolved schema violations

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-autoapicase-879a3eb2-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/autoapicase-json-change-audit-785220ed
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_6-viQ-ch1XOfOMSA8hA2H

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 autoapicase-json-change-audit-785220ed -d '<json body>'
```

Example prompt: Can you audit the change I made to my AutoAPICase JSON config — here's the before version and the after version — and tell me which fields changed, what paths were added or removed, and whether any new schema rule violations were introduced or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need schema-aware change auditing for AutoAPICase JSON documents using the pinned SchemaStore definition. It is ideal when you want both a structural diff (added/removed/changed paths via JSON pointers) and schema validation delta (introduced vs resolved violations) in a single call, rather than running a generic JSON diff or a standalone validator separately.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed or non-JSON input in before/after fields — parse error returned
- YAML or TOML input provided — not supported, only JSON accepted
- Network or payment failure — no audit result returned

## How this service works

Change audit: AutoAPICase: Audit JSON changes and validate before/after for AutoAPICase. 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 containing JSON pointers for all added, removed, and changed paths between the before and after documents, along with schema rule violations that were introduced or resolved, based on a pinned AutoAPICase SchemaStore definition. Limited to documents up to 100 KB and 32 nesting levels.

## 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/autoapicase-json-change-audit-785220ed/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)