# Change Audit: mtad.yaml

> Change Audit: mtad.yaml 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-24).

Audits JSON changes between two versions of an mtad.yaml document, validates both before and after states against a pinned SchemaStore schema, and reports added/removed/changed JSON pointers plus introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-mtad-yaml-c068289a-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-mtad-yaml-b8bf494f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sNL8FsNZtb-UkugXbfedG

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-mtad-yaml-b8bf494f -d '<json body>'
```

Example prompt: Can you audit the change I made to my mtad.yaml — here's the before and after as JSON — and tell me which paths changed, any schema rule violations that were introduced, and whether any existing errors got resolved?

## When to prefer this

Choose this endpoint when you need to audit a specific before-and-after change to an mtad.yaml (SAP MTA deployment descriptor) document, validated against a pinned SchemaStore definition. It is purpose-built for change-level diffing with schema-aware error tracking, making it ideal for CI gates, pre-deployment reviews, and regression detection. Prefer it over generic JSON diff tools when you also need schema validation context, and over general schema validators when you need to understand what changed between two revisions.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation aborted
- Invalid JSON submitted (non-parseable input) — parse error returned
- YAML or TOML input not supported — must be converted to JSON first
- Payment not completed — 402 response, no audit performed
- Network timeout or service unavailability — no response

## How this service works

Change audit: mtad.yaml: Audit JSON changes and validate before/after for mtad.yaml. 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, errors introduced by the change, and errors resolved by the change. Covers up to 100 KB per document with a maximum nesting depth of 32 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-mtad-yaml-b8bf494f/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)