# Code Climate JSON Change Auditor

> Code Climate JSON Change Auditor 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-16).

Audits and validates JSON changes (before/after documents) against a pinned Code Climate SchemaStore definition, reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-code-climate-9fa1ffe4-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/code-climate-json-change-auditor-690ea6cb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vTrWzs1BqnIT1gftSgCss

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 code-climate-json-change-auditor-690ea6cb -d '<json body>'
```

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

## When to prefer this

Choose this endpoint when you specifically need to validate Code Climate JSON configuration changes against the SchemaStore definition, especially when you want a structured diff of schema violations introduced or resolved between two document versions. Prefer this over generic JSON diff tools when Code Climate schema compliance is the goal, and over full CI pipeline validation when you only need a lightweight, instant schema audit without deployment or security guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Non-JSON input (YAML, TOML) provided — not parsed or validated
- Malformed JSON in before or after field — parse error returned
- Schema definition unavailable or pinned version mismatch — validation may be incomplete

## How this service works

Change audit: Code Climate: Audit JSON changes and validate before/after for Code Climate. 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 covering: JSON pointer locations of all added, removed, and changed paths between the before and after documents; schema rule violations present in each version; and a diff of introduced vs. resolved errors, all validated against a pinned Code Climate SchemaStore definition.

## 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/code-climate-json-change-auditor-690ea6cb/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)
