# Prettier Config Change Auditor

> Prettier 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-19).

Audits before/after changes to a .prettierrc.json file, reporting added/removed/changed JSON paths and any introduced or resolved schema validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-prettierrc-json-62a764ac-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/prettier-config-change-auditor-305c5f9b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-zcoprPxznxE5wxHqRUpY

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 prettier-config-change-auditor-305c5f9b -d '<json body>'
```

Example prompt: Can you audit my prettierrc.json change? Here's the before: {"semi":true,"tabWidth":2} and the after: {"semi":false,"tabWidth":4,"printWidth":100} — tell me what paths changed and if any schema violations were introduced or resolved.

## When to prefer this

Choose this endpoint when you need to validate a specific change to a .prettierrc.json file against the SchemaStore definition, especially when you want to know not just whether the new config is valid, but also what changed and whether the change introduced or resolved any errors. It is purpose-built for prettier configuration files specifically, not general JSON diffing or validation of other config formats.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Malformed JSON input (not valid JSON) — parsing error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment processing failure — no result returned

## How this service works

Change audit: prettierrc.json: Audit JSON changes and validate before/after for prettierrc.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 diff of the two prettierrc.json documents, including JSON pointers for added, removed, and changed paths, a list of schema rule violations per path, and a summary of errors that were introduced or resolved between the before and after states.

## 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/prettier-config-change-auditor-305c5f9b/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)