# Change Audit: buf.lock

> Change Audit: buf.lock 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-19).

Validates and audits JSON changes between two buf.lock document versions, reporting added/removed/changed paths and introduced/resolved schema errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-buf-lock-341f4844-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-buf-lock-e8ca35f5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_m4iXfjjIJej414MzSNPNC

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-buf-lock-e8ca35f5 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new buf.lock JSON files, tell me what paths were added, removed, or changed, and flag any new schema violations introduced?

## When to prefer this

Use this endpoint when you need to audit changes specifically to buf.lock JSON files against a pinned SchemaStore definition, particularly when you want both a structural diff (added/removed/changed paths) and schema compliance checking in a single call for under $0.01 USDC. Prefer it over generic JSON diff tools when buf.lock schema awareness and rule violation tracking matter.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Malformed JSON submitted as before or after — validation error returned
- YAML or TOML input format — not supported, must be JSON
- Network or payment processing failure — no result returned

## How this service works

Change audit: buf.lock: Audit JSON changes and validate before/after for buf.lock. 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, along with schema rule violations that were introduced or resolved, using a pinned SchemaStore definition for buf.lock.

## 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-buf-lock-e8ca35f5/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)