# Docker Bake Change Audit

> Docker Bake 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-23).

Validates and audits JSON changes between before/after docker bake configuration documents, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-docker-bake-4eefaeaf-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-bake-change-audit-17376b9c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ohso9s4G-457yxFqDWPCH

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-bake-change-audit-17376b9c -d '<json body>'
```

Example prompt: Can you audit the changes I made to my docker bake JSON config? Here's the before: {"target":{"app":{"context":".","dockerfile":"Dockerfile"}}} and after: {"target":{"app":{"context":"./src","dockerfile":"Dockerfile","tags":["myapp:latest"]}}} — tell me what paths changed and if any schema rules were broken or fixed.

## When to prefer this

Choose this endpoint when you need to audit schema-level changes between two docker bake JSON configurations, specifically to catch introduced or resolved schema violations alongside a structural diff. It is distinct from generic JSON diff tools because it applies a pinned SchemaStore definition specifically for docker bake, giving domain-aware rule violation reporting rather than just structural comparison.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — validation refused
- Invalid JSON submitted as before or after — parse error returned
- YAML or TOML format submitted instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: docker bake: Audit JSON changes and validate before/after for docker bake. 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 audit report containing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved according to a pinned SchemaStore definition for docker bake. Up to 100 KB per document is supported.

## 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-bake-change-audit-17376b9c/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)