# Azure IoT Edge Deployment Template Change Audit

> Azure IoT Edge Deployment Template 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-22).

Validates and diffs two Azure IoT Edge deployment template JSON documents, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-azure-iot-edge-deployment--5ec47850-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/azure-iot-edge-deployment-template-change-audit-09b1119f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PQ1xzW-1tDTbbsekvHjAJ

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 azure-iot-edge-deployment-template-change-audit-09b1119f -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new Azure IoT Edge deployment template JSONs — I want to know which paths were added, removed, or changed, and whether any new schema violations were introduced or old ones were resolved?

## When to prefer this

Use this endpoint when you need schema-aware diffing of Azure IoT Edge deployment template JSON specifically, with violations mapped to SchemaStore rules. Prefer it over generic JSON diff tools when you need to know not just what changed but whether the change introduced or fixed schema violations against the official Azure IoT Edge deployment template schema.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting depth exceeds 32 levels — rejected with depth error
- Malformed JSON input (non-parseable) — returns parse error
- YAML or TOML input provided instead of JSON — not supported, returns format error
- Payment not included or insufficient — x402 payment required response

## How this service works

Change audit: Azure IoT Edge deployment template: Audit JSON changes and validate before/after for Azure IoT Edge deployment template. 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 of JSON pointer-level differences between the before and after documents (added, removed, and changed paths), along with schema rule violations present in each version, indicating which errors were introduced by the change and which were resolved. Covers documents up to 100 KB and up to 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/azure-iot-edge-deployment-template-change-audit-09b1119f/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)