# Change Audit: Avro Avsc

> Change Audit: Avro Avsc 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 diffs two JSON documents representing Avro AVSC schemas, reporting added/removed/changed paths and introduced/resolved validation errors using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-avro-avsc-59b2c7f4-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/change-audit-avro-avsc-d41ba81d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j_qrfVcBRYYEG6QoOiHrw

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-avro-avsc-d41ba81d -d '<json body>'
```

Example prompt: Audit my Avro AVSC schema change — here's the before version and the after version — and tell me what paths changed, what validation rules are now violated, and whether any new errors were introduced or old ones resolved.

## When to prefer this

Choose this endpoint when you need to audit the delta between two versions of an Avro AVSC schema document and want both a structural diff (added/removed/changed JSON paths) and a validation pass (SchemaStore rule violations) in a single call. It is purpose-built for Avro AVSC and uses a pinned schema definition, making it more reliable than a generic JSON differ for Avro-specific rule enforcement. Best for CI/CD schema change review, PR auditing, or migration safety checks on documents under 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is not valid JSON (e.g. YAML or TOML) — parsing not supported, error returned
- Payment not included or insufficient USDC — request blocked
- Malformed request body missing before/after fields — validation error

## How this service works

Change audit: Avro Avsc: Audit JSON changes and validate before/after for Avro Avsc. 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 pointer paths that were added, removed, or changed between the before and after documents, along with any SchemaStore rule violations introduced or resolved, based on a pinned Avro AVSC schema definition.

## 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-avro-avsc-d41ba81d/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)