# PostCSS Config Change Audit (.postcssrc)

> PostCSS Config Change Audit (.postcssrc) 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 to a .postcssrc PostCSS configuration file, validating both documents against a pinned SchemaStore definition and reporting added, removed, or changed paths along with introduced or resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-postcssrc-9605195e-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/postcss-config-change-audit-postcssrc-bef1949f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gAT6xb03JdESingTwQgeS

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 postcss-config-change-audit-postcssrc-bef1949f -d '<json body>'
```

Example prompt: Can you audit my .postcssrc changes and tell me if I introduced any schema errors? Here's the before: {} and the after: {"plugins":{"autoprefixer":{}}} — use the SchemaStore-backed change audit to flag added paths and any rule violations.

## When to prefer this

Choose this endpoint when you specifically need to validate changes to a .postcssrc PostCSS configuration file using a pinned SchemaStore definition, and want a structured diff of added/removed/changed JSON paths alongside introduced or resolved schema errors. It is ideal for CI pipelines, code review automation, or agent workflows that need to gate on config correctness. Not suitable for YAML/TOML configs, non-PostCSS schemas, or files over 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Non-JSON input (YAML, TOML) — not parsed, will fail or produce incorrect results
- Malformed JSON in before or after field — validation cannot proceed
- Schema unavailable or pinned definition mismatch — may return incomplete results

## How this service works

Change audit: .postcssrc: Audit JSON changes and validate before/after for .postcssrc. 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 report including JSON pointers for added, removed, and changed configuration paths between the before and after documents, plus a list of schema rule violations introduced or resolved in the transition, validated against a pinned SchemaStore definition for .postcssrc.

## 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/postcss-config-change-audit-postcssrc-bef1949f/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)