# jsconfig.json Change Audit

> jsconfig.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-22).

Validates and audits before/after JSON changes for jsconfig.json, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-jsconfig-json-da7ac4f2-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jsconfig-json-change-audit-773774b8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qiQcMWe-MXCYDxIFvKR56

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 jsconfig-json-change-audit-773774b8 -d '<json body>'
```

Example prompt: Can you audit my jsconfig.json changes and tell me which paths were added, removed, or changed, and whether any schema violations were introduced? Here's the before version: {} and after version: {"compilerOptions":{"target":"ES6","moduleResolution":"node"}}.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a jsconfig.json file against its SchemaStore schema definition, comparing two versions to surface added/removed/changed paths and schema violations. Prefer this over generic JSON diff tools when you need schema-aware validation tied to the jsconfig.json specification, not just structural diffing.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON submitted (not parseable) — error returned
- YAML or TOML input not supported — must be valid JSON
- Malformed request body — schema validation error

## How this service works

Change audit: jsconfig.json: Audit JSON changes and validate before/after for jsconfig.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 listing added, removed, and changed JSON pointer paths between the before and after documents, along with any schema rule violations that were introduced or resolved, validated against a pinned SchemaStore definition for jsconfig.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/jsconfig-json-change-audit-773774b8/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)