# JSHintRC Change Audit

> JSHintRC 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-14).

Audits JSON changes between two .jshintrc documents, reporting added/removed/changed paths and introduced/resolved rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-jshintrc-a4e33fc0-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/jshintrc-change-audit-d91d85de
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_jPVtDu4OKRqBdcjEbvR1A

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 jshintrc-change-audit-d91d85de -d '<json body>'
```

Example prompt: Can you audit my .jshintrc change? Here's the before: {} and after: {"undef": true, "esversion": 6} — tell me what paths changed and whether any new rule violations were introduced.

## When to prefer this

Use this endpoint when you specifically need to audit changes to a .jshintrc configuration file between two JSON states, with schema validation backed by a pinned SchemaStore definition. Prefer it over generic JSON diff tools when you need jshint-specific rule violation tracking (introduced/resolved errors) rather than a plain structural diff.

## Known failure modes

- Document exceeds 100 KB size limit — request rejected
- JSON depth exceeds 32 levels — parsing refused
- Invalid JSON submitted (non-parseable) — validation cannot proceed
- YAML or TOML format submitted instead of JSON — not supported
- Network or payment processing failure — no audit returned

## How this service works

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

## 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/jshintrc-change-audit-d91d85de/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)