# Change Audit: .build.yml Schema Validator

> Change Audit: .build.yml Schema 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).

Audits JSON changes to .build.yml by comparing before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-build-yml-797c21c8-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/change-audit-build-yml-schema-validator-661a17d3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TRGsa8O7muxGSN2uIW2Xc

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-build-yml-schema-validator-661a17d3 -d '<json body>'
```

Example prompt: Audit my .build.yml change — here's the before: {} and after: {"image":"archlinux","packages":["git"]} — tell me what paths changed, what schema rules were violated, and whether any errors were introduced or resolved.

## When to prefer this

Choose this endpoint when you need to audit a specific change to a .build.yml CI configuration file, particularly when you want to know not just whether the final document is valid but how validity changed between versions — what errors were introduced or resolved by the edit. It is purpose-built for .build.yml using a pinned SchemaStore definition, making it more reliable for that format than a generic JSON Schema validator. Not suitable for YAML/TOML inputs or for deployment or security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after fields — parse error returned
- Input is YAML or TOML rather than JSON — not supported, no parsing performed
- SchemaStore definition mismatch for unusual .build.yml variants — may produce false positives

## How this service works

Change audit: .build.yml: Audit JSON changes and validate before/after for .build.yml. 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 of JSON pointer paths that were added, removed, or changed between the before and after documents, along with schema rule violations for each version and a diff of introduced versus resolved validation errors based on the pinned SchemaStore .build.yml 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-build-yml-schema-validator-661a17d3/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)