# Babel Config Change Auditor (babelrc.json)

> Babel Config Change Auditor (babelrc.json) 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-18).

Audits JSON changes in babelrc.json files by comparing before/after documents against a pinned SchemaStore definition, reporting added/removed/changed paths and introduced/resolved validation errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-babelrc-json-c05802b2-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/babel-config-change-auditor-babelrc-json-6f7d0a78
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xyAoLxoimwpEs2WtQSuXq

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 babel-config-change-auditor-babelrc-json-6f7d0a78 -d '<json body>'
```

Example prompt: Can you audit my babelrc.json change — here's the before version: {} and the after version: {"presets": ["@babel/preset-env"], "plugins": ["@babel/plugin-transform-runtime"]} — tell me what paths changed and whether any schema violations were introduced or resolved?

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a babelrc.json file against its SchemaStore-pinned JSON schema, and want a structured diff of added/removed/changed paths plus introduced/resolved validation errors. It is purpose-built for Babel configuration files and uses a pinned schema definition, making it more precise than a generic JSON differ or general-purpose schema validator for this specific file type.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted as before or after value — parse error returned
- Schema unavailable or definition mismatch — validation may be incomplete
- Network or payment failure — no result returned

## How this service works

Change audit: babelrc.json: Audit JSON changes and validate before/after for babelrc.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 identifying JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations introduced or resolved by the change, based on a pinned SchemaStore definition for babelrc.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/babel-config-change-auditor-babelrc-json-6f7d0a78/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)