# Change Audit: imageoptimizer.json

> Change Audit: imageoptimizer.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-19).

Validates and audits before/after changes to imageoptimizer.json files, reporting JSON pointer diffs, rule violations, added/removed/changed paths, and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-imageoptimizer-json-9b90f3f8-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-imageoptimizer-json-81cf4b17
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tXHfE8qDBxo2dJ0gTIOGO

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-imageoptimizer-json-81cf4b17 -d '<json body>'
```

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

## When to prefer this

Use this endpoint when you specifically need to audit changes to an imageoptimizer.json configuration file against its pinned SchemaStore definition. It is purpose-built for before/after diff and validation of this exact file type, making it more reliable than a generic JSON differ or schema validator for this format. Prefer it when you want both structural diff (added/removed/changed paths) and schema compliance checking in a single call.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- Payment not included or insufficient — x402 payment required response
- Schema definition unavailable — validation may be incomplete

## How this service works

Change audit: imageoptimizer.json: Audit JSON changes and validate before/after for imageoptimizer.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, schema rule violations present in each version, newly introduced errors, and errors that were resolved. Documents must be under 100 KB and within 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/change-audit-imageoptimizer-json-81cf4b17/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)