# Lerna.json Change Audit

> Lerna.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-22).

Validates and audits before/after JSON changes for lerna.json files using a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved errors.

## Facts

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

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 lerna-json-change-audit-d043ce9b -d '<json body>'
```

Example prompt: Audit my lerna.json change — here's the before: {} and the after with the new version and packages fields added — tell me which paths changed and whether any schema violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you need schema-aware diff analysis specifically for lerna.json configuration files, particularly when you want to know not just what changed structurally but also whether changes introduced or resolved JSON Schema violations per the official SchemaStore definition. Prefer this over generic JSON diff tools when lerna monorepo config correctness matters.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON provided in before or after fields — parse error returned
- Malformed request body — validation error response
- Network or payment processing failure — 402 or 5xx error

## How this service works

Change audit: lerna.json: Audit JSON changes and validate before/after for lerna.json. 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 listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, referencing the pinned SchemaStore definition for lerna.json.

## 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/lerna-json-change-audit-d043ce9b/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)