# bpkg JSON Change Audit

> bpkg JSON Change Audit 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-16).

Audits before/after JSON document pairs against the bpkg SchemaStore schema, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-bpkg-1f1a95e8-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bpkg-json-change-audit-c419bd19
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_J9hjkdpF0billFIusHBUu

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 bpkg-json-change-audit-c419bd19 -d '<json body>'
```

Example prompt: Can you audit my bpkg config change — here's the before and after JSON — and tell me which paths were added, removed, or changed, and whether any new schema errors were introduced or old ones resolved?

## When to prefer this

Use this endpoint when you specifically need to audit changes to bpkg package configuration files against the SchemaStore schema definition, getting both a structural diff (added/removed/changed paths) and schema validation delta (introduced/resolved errors) in a single call. Prefer this over generic JSON diff tools when bpkg-specific schema compliance matters, or over generic schema validators when you need to understand what changed between two versions rather than just whether one version is valid.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Input is not valid JSON (YAML/TOML not supported) — parse error returned
- Malformed request body — validation error
- Payment of 0.01 USDC not fulfilled — 402 response

## How this service works

Change audit: bpkg: Audit JSON changes and validate before/after for bpkg. 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 including JSON pointer paths for all added, removed, and changed fields between the before and after documents, along with a list of schema rule violations introduced and resolved, referencing the pinned bpkg SchemaStore definition. Each call covers one two-document comparison up to 100 KB per document.

## 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/bpkg-json-change-audit-c419bd19/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)