# npm-badges JSON Change Audit

> npm-badges 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-14).

Validates and audits JSON changes for npm-badges schemas, reporting added/removed/changed paths and introduced/resolved validation errors between a before and after document.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-npm-badges-cb577a0c-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/npm-badges-json-change-audit-393c282e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_pdsr_mPyACbJk8JnMRm9R

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 npm-badges-json-change-audit-393c282e -d '<json body>'
```

Example prompt: Can you audit the changes I made to my npm-badges JSON? Here's the before version: {} and the after version: {"name":"my-package","badge":"coverage","style":"flat"} — tell me what paths changed and whether any new schema violations were introduced.

## When to prefer this

Use this endpoint when you specifically need to audit JSON changes against the npm-badges SchemaStore schema definition, comparing a before and after document pair to detect introduced or resolved validation errors and structural path changes. Prefer this over generic JSON diff tools when npm-badges schema compliance is the goal and you need violation-level reporting tied to a known schema version.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting deeper than 32 levels — parsing refused
- Invalid JSON submitted as before or after — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Schema definition unavailable or pinned version mismatch — audit may be incomplete

## How this service works

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

## 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/npm-badges-json-change-audit-393c282e/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)