# Change Audit: Claude Code Settings

> Change Audit: Claude Code Settings 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).

Audits JSON changes to Claude Code Settings files by comparing before/after documents, validating both against a pinned SchemaStore definition, and reporting added/removed/changed paths plus introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-claude-code-settings-f6875f71-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-claude-code-settings-d0934b44
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aHWNzFj2hUy5gwuNWFJKd

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-claude-code-settings-d0934b44 -d '<json body>'
```

Example prompt: Can you audit my Claude Code Settings change — here's the before JSON and the after JSON — and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint specifically when you need to validate changes to Claude Code Settings JSON files against the authoritative SchemaStore definition, and want a diff-style report of added/removed/changed paths alongside before/after validation status. Prefer this over generic JSON diff tools when schema-aware violation tracking and error introduction/resolution reporting are needed for Claude Code Settings specifically.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting exceeds 32 levels — rejected with depth error
- Malformed JSON submitted as before or after — parse error returned
- Schema definition unavailable or stale on host — validation may be incomplete
- Non-JSON formats (YAML, TOML) are not supported and will fail to parse

## How this service works

Change audit: Claude Code Settings: Audit JSON changes and validate before/after for Claude Code Settings. 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 of JSON pointer differences (added, removed, and changed paths) between the before and after documents, along with validation results for each document against the pinned Claude Code Settings SchemaStore schema, highlighting newly introduced errors and resolved errors across the change.

## 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-claude-code-settings-d0934b44/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)