# BX CI JSON Change Auditor

> BX CI 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 JSON document changes between a before and after version, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition for BX CI.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-bx-ci-fe2697b0-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/bx-ci-json-change-auditor-440c224f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_05IE2hs_C3lzMFClwqXZH

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 bx-ci-json-change-auditor-440c224f -d '<json body>'
```

Example prompt: Can you audit the changes I made to my BX CI config — here's the old JSON and the new JSON — and tell me what paths changed, what was added or removed, and whether any schema rule violations were introduced or resolved?

## When to prefer this

Choose this endpoint when you need to audit the exact structural and schema-level differences between two versions of a BX CI JSON configuration, especially when you want both a diff of paths and a report of schema rule violations introduced or resolved. It uses a pinned SchemaStore definition specific to BX CI, making it more targeted than a generic JSON diff tool. Not suitable for YAML/TOML configs, documents over 100 KB, or deployment/security guarantees.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Input is YAML or TOML instead of JSON — not supported
- Malformed JSON in before or after field — parse error returned
- Network or service unavailability — HTTP error response

## How this service works

Change audit: BX CI: Audit JSON changes and validate before/after for BX CI. 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 all added, removed, and changed paths between the before and after documents, along with any schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for BX CI. Limited to documents up 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/bx-ci-json-change-auditor-440c224f/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)