# Claude Code Keybindings JSON Change Audit

> Claude Code Keybindings 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-19).

Audits before/after JSON changes for Claude Code Keybindings configuration, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-claude-code-keybindings-1c20d2aa-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/claude-code-keybindings-json-change-audit-fc9fbc70
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_lXlep6Hag0xrWAON7a0ys

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 claude-code-keybindings-json-change-audit-fc9fbc70 -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you need to validate a specific before/after change to a Claude Code keybindings JSON file against the official SchemaStore schema. It is purpose-built for keybindings config audits with path-level diffing and schema violation tracking, not for general-purpose JSON diffing or other config file formats.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing fails
- Malformed JSON input (non-parseable) — validation cannot proceed
- YAML or TOML input instead of JSON — not supported
- Missing or empty after field — incomplete audit

## How this service works

Change audit: Claude Code Keybindings: Audit JSON changes and validate before/after for Claude Code Keybindings. 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 that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, validated against a pinned SchemaStore definition for Claude Code Keybindings.

## 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/claude-code-keybindings-json-change-audit-fc9fbc70/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)