# bun.lock Change Audit

> bun.lock 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-24).

Validates and diffs two bun.lock JSON documents, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-bun-lock-d50201cd-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bun-lock-change-audit-5479f508
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MC4jWE6K_fEV-y0SSlMB0

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 bun-lock-change-audit-5479f508 -d '<json body>'
```

Example prompt: Can you audit my bun.lock changes — here's the before version and the after version — and tell me what paths were added, removed, or changed, and whether any schema rule violations were introduced or resolved?

## When to prefer this

Choose this endpoint when you need to audit structural and schema-level changes to a bun.lock file specifically, using a pinned SchemaStore definition. It is ideal for CI pipelines, PR review automation, or dependency upgrade validation where you need precise JSON pointer diffs and schema compliance checking — not just a raw text diff.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Network timeout or service unavailability — no result returned

## How this service works

Change audit: bun.lock: Audit JSON changes and validate before/after for bun.lock. 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 listing JSON pointers for all added, removed, and changed paths between the before and after documents, plus any schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition for bun.lock.

## 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/bun-lock-change-audit-5479f508/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)