# compile_commands.json Change Audit

> compile_commands.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-24).

Audits JSON changes between before/after versions of compile_commands.json, validating both against a pinned SchemaStore schema and reporting added/removed/changed paths and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-compile-commands-json-eaa48d00-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/compile-commands-json-change-audit-38e8e03c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wgkTaN9BQmQ7yWfJ0dQIl

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 compile-commands-json-change-audit-38e8e03c -d '<json body>'
```

Example prompt: Can you audit the changes I made to my compile_commands.json — here's the old version and the new version — and tell me if I introduced any schema violations, what paths changed, and whether any errors were resolved or added?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to compile_commands.json files used in C/C++ build systems, with validation against the authoritative SchemaStore schema definition. It is ideal for CI pipelines, code review automation, or developer agents that need to catch schema regressions between two versions of the file. It is not suitable for general JSON diffing, YAML/TOML validation, or other JSON schema types.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- Nesting depth exceeds 32 levels — request rejected
- Invalid JSON submitted (not parseable) — validation cannot proceed
- YAML or TOML input not supported — must be valid JSON
- Network or payment processing failure — no result returned

## How this service works

Change audit: compile_commands.json: Audit JSON changes and validate before/after for compile_commands.json. 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 including JSON pointers for all added, removed, and changed paths between the before and after documents, a list of schema rule violations present in each version, and a summary of errors introduced or resolved by the change. Both documents are validated against a pinned SchemaStore definition for compile_commands.json.

## 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/compile-commands-json-change-audit-38e8e03c/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)