# buf.work.yaml Change Audit Validator

> buf.work.yaml Change Audit Validator 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-18).

Validates and audits JSON changes between before/after versions of a buf.work.yaml configuration file, reporting added/removed/changed paths and rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-buf-work-yaml-33312714-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/buf-work-yaml-change-audit-validator-bfbea206
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wtUKO2doFp0ehLis4H-yf

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 buf-work-yaml-change-audit-validator-bfbea206 -d '<json body>'
```

Example prompt: Can you audit my buf.work.yaml change and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced? Here's the before: {} and after: {"version": "v1", "directories": ["proto"]}.

## When to prefer this

Choose this endpoint when you need a focused, schema-aware diff of buf.work.yaml configuration changes specifically validated against a pinned SchemaStore definition. It is ideal for CI/CD gates, pre-merge checks, or debugging Buf workspace configuration regressions where you need precise JSON pointer reporting rather than a generic JSON diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Non-JSON input (YAML/TOML) submitted — not parsed, no result
- Invalid JSON structure in before or after field — validation error
- Network or payment processing failure — no result returned

## How this service works

Change audit: buf.work.yaml: Audit JSON changes and validate before/after for buf.work.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, along with any rule violations introduced or resolved relative to the pinned SchemaStore definition for buf.work.yaml.

## 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/buf-work-yaml-change-audit-validator-bfbea206/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)