# Mocharc Change Audit

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

Validates and audits JSON changes between two .mocharc configuration documents, reporting added/removed/changed paths and schema rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-mocharc-117257b6-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/mocharc-change-audit-0e631155
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_fBQE0UXPrSmDqergzkyUJ

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 mocharc-change-audit-0e631155 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new .mocharc configs — here's the before: {} and after: {"spec":"test/**/*.spec.js","timeout":5000} — and tell me what paths changed, what was added or removed, and whether any SchemaStore rule violations were introduced?

## When to prefer this

Use this endpoint when you specifically need to audit changes to a .mocharc configuration file against the SchemaStore JSON schema definition. It is ideal for CI pipelines, PR review automation, or pre-commit hooks where you want to catch schema violations introduced by config edits and get a structured diff of JSON pointer changes. Prefer this over generic JSON diff tools when you need schema-aware validation tied specifically to the Mocha test runner configuration format.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting depth exceeds 32 levels — request rejected
- Non-JSON input (YAML or TOML) — not parsed, may fail silently or error
- Invalid JSON syntax in before or after field — parse error returned
- SchemaStore definition unavailable — validation results may be incomplete

## How this service works

Change audit: .mocharc: Audit JSON changes and validate before/after for .mocharc. 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

A structured report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations introduced or resolved, based on the pinned SchemaStore definition for .mocharc.

## 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/mocharc-change-audit-0e631155/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)