# Change Audit: Helmfile Schema Validator

> Change Audit: Helmfile Schema Validator 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 audits JSON changes to helmfile configurations by comparing before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-helmfile-a640e183-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/change-audit-helmfile-schema-validator-34016ea3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_prn1Lli4Fl0CAkqAOOtdc

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-helmfile-schema-validator-34016ea3 -d '<json body>'
```

Example prompt: Can you audit my helmfile config changes? Here's the before: {} and after: {releases: [{name: 'myapp', chart: 'stable/myapp'}]} — tell me what paths changed and if any schema violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you need schema-aware change auditing specifically for helmfile configurations, using a pinned SchemaStore definition for reproducible results. It is ideal for pre-deploy validation workflows, PR reviews, or CI checks where you want a deterministic JSON diff plus rule violation tracking. It does not perform YAML parsing, deployment execution, or security scanning, so use it purely for schema correctness auditing of JSON-represented helmfile documents.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input not supported — must be converted to JSON first
- Payment of 0.01 USDC not completed — request blocked

## How this service works

Change audit: helmfile: Audit JSON changes and validate before/after for helmfile. 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 containing JSON pointers for all added, removed, and changed paths between the before and after documents, along with any schema rule violations introduced or resolved by the change, based on a pinned SchemaStore helmfile definition. Each document is limited to 100 KB and 32 nesting levels.

## 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-helmfile-schema-validator-34016ea3/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)