# SARIF 2.1.0-rtm.2 JSON Change Audit

> SARIF 2.1.0-rtm.2 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-19).

Validates and diffs two JSON documents against the SARIF 2.1.0-rtm.2 schema, reporting added/removed/changed paths and introduced/resolved rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-sarif-2-1-0-rtm-2-3f9df543-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/sarif-2-1-0-rtm-2-json-change-audit-a2d8ce75
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k-rYqyoYfiJ3DJKU7Y5_y

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 sarif-2-1-0-rtm-2-json-change-audit-a2d8ce75 -d '<json body>'
```

Example prompt: Compare these two SARIF 2.1.0-rtm.2 JSON documents and tell me what paths changed, what rule violations were introduced or resolved, and whether both are valid: here's the before doc and here's the after doc.

## When to prefer this

Choose this endpoint when you specifically need change auditing for SARIF 2.1.0-rtm.2 JSON documents — comparing a before and after state, identifying structural diffs at the JSON pointer level, and tracking which schema violations were introduced or resolved. Prefer this over generic JSON diff tools when you need schema-aware validation tied to the SARIF 2.1.0-rtm.2 SchemaStore definition.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing refused
- Invalid JSON syntax in before or after field — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- Both documents identical — diff report shows no changes

## How this service works

Change audit: sarif-2.1.0-rtm.2: Audit JSON changes and validate before/after for sarif-2.1.0-rtm.2. 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 change audit report listing JSON pointer paths that were added, removed, or modified between the before and after documents; rule violations present in each; errors introduced by the change; and errors resolved by the change — all validated against the pinned SARIF 2.1.0-rtm.2 SchemaStore 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/sarif-2-1-0-rtm-2-json-change-audit-a2d8ce75/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)