# Docker Desktop Extension Metadata Change Auditor

> Docker Desktop Extension Metadata Change Auditor 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-23).

Audits JSON changes between two Docker Desktop extension metadata documents, reporting added/removed/changed paths and schema validation errors against a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-docker-desktop-extension-m-7730f960-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/docker-desktop-extension-metadata-change-auditor-45a2bf45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pzyyRvBJIyZHGtc3ycXd8

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 docker-desktop-extension-metadata-change-auditor-45a2bf45 -d '<json body>'
```

Example prompt: Can you audit the changes I made to my Docker Desktop extension metadata JSON? Here's the before version and the after version — I want to know what paths changed and whether I introduced any new schema validation errors.

## When to prefer this

Use this endpoint when you specifically need to validate and diff Docker Desktop extension metadata JSON against the SchemaStore schema definition, and want a structured change report with pointer-level granularity. Prefer it over generic JSON diff tools when schema compliance checking against the Docker Desktop extension schema is required alongside structural diffing.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON input — parse error returned
- Invalid or non-JSON content type submitted — error returned
- SchemaStore definition unavailable or outdated — validation may be incomplete

## How this service works

Change audit: Docker Desktop extension metadata: Audit JSON changes and validate before/after for Docker Desktop extension metadata. 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

A structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations present in each version, newly introduced errors, and errors that were resolved — validated against a pinned SchemaStore definition for Docker Desktop extension metadata.

## 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/docker-desktop-extension-metadata-change-auditor-45a2bf45/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)