# buf.plugin.yaml Change Audit & Validator

> buf.plugin.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-14).

Audits JSON changes between before/after versions of a buf.plugin.yaml document, reporting added/removed/changed paths and introduced/resolved schema validation errors.

## Facts

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

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-plugin-yaml-change-audit-validator-9798eade -d '<json body>'
```

Example prompt: Can you audit the changes I made to my buf.plugin.yaml? Here's the before version and the after version — I want to know what paths changed and whether any new schema rule violations were introduced or old ones got fixed.

## When to prefer this

Choose this endpoint when you need to audit incremental changes to a buf.plugin.yaml configuration file, specifically to catch schema violations introduced by edits. It is ideal for CI pipelines or agent-assisted code review where you need a structured diff of JSON paths alongside SchemaStore-based validation errors. Not suitable for YAML/TOML input, files over 100 KB, or deployment/security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is not valid JSON — parse error returned
- YAML or TOML format submitted instead of JSON — not parsed
- Schema definition unavailable or stale — validation may be incomplete

## How this service works

Change audit: buf.plugin.yaml: Audit JSON changes and validate before/after for buf.plugin.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

A structured report listing all JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced in the after document or resolved compared to the before document, based on a pinned SchemaStore definition for buf.plugin.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-plugin-yaml-change-audit-validator-9798eade/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)