# Pre-commit Config Change Auditor

> Pre-commit Config 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-15).

Audits JSON-encoded before/after documents for .pre-commit-config.yml, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-pre-commit-config-yml-5f4e4082-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pre-commit-config-change-auditor-f7f555c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GtFTK2HK1eS6nNmJ-Er4R

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 pre-commit-config-change-auditor-f7f555c9 -d '<json body>'
```

Example prompt: Can you audit the change I made to my .pre-commit-config.yml — here's the before version and here's the after version — and tell me which paths changed and whether any new schema violations were introduced or old ones got fixed?

## When to prefer this

Choose this endpoint when you need to specifically audit a change to a .pre-commit-config.yml file, comparing before and after states and getting schema-validated diff output. Prefer it over generic JSON diff tools when you want SchemaStore-backed rule violation reporting scoped to pre-commit configuration. Not suitable for YAML/TOML input, files over 100 KB, or security/deployment guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing fails
- Input is YAML or TOML rather than JSON — not supported
- Malformed JSON in before or after field — parse error
- Network or payment processing failure — no result returned

## How this service works

Change audit: .pre-commit-config.yml: Audit JSON changes and validate before/after for .pre-commit-config.yml. 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 pointers for all added, removed, and changed paths between the before and after documents, along with schema rule violations present in each, newly introduced errors, and errors that were resolved — all validated against a pinned SchemaStore definition for .pre-commit-config.yml.

## 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/pre-commit-config-change-auditor-f7f555c9/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)