# Azure Container App Template Change Audit

> Azure Container App 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-15).

Validates and audits JSON changes between before/after versions of an Azure Container App immutable revision template, reporting added/removed/changed paths and schema rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-azure-container-app-templa-ee5755e7-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/azure-container-app-template-change-audit-68946355
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_a_BziICC8pSGNpon-yPyr

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-container-app-template-change-audit-68946355 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new Azure Container App immutable revision template JSON configs — I want to see which paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you need a structured, schema-aware diff of Azure Container App immutable revision template JSON specifically — especially when you want to surface not just structural changes (added/removed/changed paths) but also schema rule violations tied to those changes. Prefer this over generic JSON diff tools when compliance with the Azure Container App SchemaStore definition matters, or when you need to track whether a change introduced or resolved validation errors.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting exceeds 32 levels — rejected with depth error
- Invalid JSON submitted (e.g. YAML or TOML) — not parsed, returns parse error
- Before or after field missing — may default to empty object
- Schema definition unavailable or mismatched — validation results may be incomplete

## How this service works

Change audit: Azure Container App template for defining an immutable revision: Audit JSON changes and validate before/after for Azure Container App template for defining an immutable revision. 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 differences between the before and after documents, including added, removed, and changed paths, schema rule violations tied to specific pointers, and a list of newly introduced or resolved errors based on the pinned SchemaStore definition for Azure Container App immutable revision templates.

## 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-container-app-template-change-audit-68946355/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)