# Change Audit: Helm Chart.lock

> Change Audit: Helm Chart.lock 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-12).

Validates and diffs two JSON representations of a Helm Chart.lock file, reporting added/removed/changed paths and schema rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-helm-chart-lock-46e1e0f4-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-helm-chart-lock-e89d1104
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BqcRkHz7_80kPuXZ1XmWl

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 change-audit-helm-chart-lock-e89d1104 -d '<json body>'
```

Example prompt: Can you audit my Helm Chart.lock changes — here's the before JSON 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

Choose this endpoint when you specifically need to audit changes between two versions of a Helm Chart.lock file and validate both against a SchemaStore schema definition. It is purpose-built for Helm Chart.lock rather than generic JSON diff or general Helm chart validation, making it more precise for this file type.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — validation cannot proceed
- Network or payment processing error — no result returned
- SchemaStore definition unavailable or pinned version mismatch — may affect rule accuracy

## How this service works

Change audit: Helm Chart.lock: Audit JSON changes and validate before/after for Helm Chart.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 pointer paths for every added, removed, and changed field between the before and after documents, along with any schema rule violations introduced or resolved, all validated against a pinned SchemaStore definition for Helm Chart.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/change-audit-helm-chart-lock-e89d1104/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)