# KODE/CI build.yaml JSON Change Auditor

> KODE/CI build.yaml JSON Change Auditor 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 before/after JSON changes for KODE/CI build.yaml files, reporting added/removed/changed paths, JSON pointer violations, and schema rule changes against a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-kode-ci-build-yaml-d8a6d403-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/kode-ci-build-yaml-json-change-auditor-cafa2d14
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_UCdUSmJyX88KKlt9SdPdC

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 kode-ci-build-yaml-json-change-auditor-cafa2d14 -d '<json body>'
```

Example prompt: Can you audit the change I made to my KODE/CI build.yaml — here's the before and after JSON — and tell me which fields were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint when you specifically need to audit changes to KODE/CI build.yaml configuration files in JSON format against a pinned SchemaStore schema. It is purpose-built for before/after change diffing with schema-aware violation tracking, making it ideal for CI/CD pipelines, pre-merge checks, and configuration drift analysis. Prefer this over generic JSON diff tools when you need schema rule context alongside structural change detection.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation aborted
- Input is not valid JSON (YAML/TOML not supported) — parse error returned
- SchemaStore definition unavailable or pinned version mismatch — audit may be incomplete
- Malformed request body missing before or after fields — error response

## How this service works

Change audit: KODE/CI build.yaml: Audit JSON changes and validate before/after for KODE/CI build.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 audit report including JSON pointers for rule violations, lists of added/removed/changed paths between the before and after documents, and a breakdown of introduced versus resolved schema errors based on the pinned SchemaStore definition for KODE/CI build.yaml. Documents are limited to 100 KB and 32 nesting levels each.

## 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/kode-ci-build-yaml-json-change-auditor-cafa2d14/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)