# Change Audit: Elgato Stream Deck JSON Validator

> Change Audit: Elgato Stream Deck JSON Validator 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-18).

Validates and audits before/after JSON changes for Elgato Stream Deck configurations using a pinned SchemaStore definition, reporting added/removed/changed paths and rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-elgato-stream-deck-d08b353f-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/change-audit-elgato-stream-deck-json-validator-37e838e6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dFNp1RRDMZNQOyx5c8SDT

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 change-audit-elgato-stream-deck-json-validator-37e838e6 -d '<json body>'
```

Example prompt: Can you audit the changes between my old and new Elgato Stream Deck JSON profile? Here's the before config and the after config — I want to know what paths changed, what was added or removed, and whether any new schema violations were introduced.

## When to prefer this

Choose this endpoint when you specifically need schema-aware change auditing for Elgato Stream Deck JSON configurations using the pinned SchemaStore definition. It is purpose-built for Stream Deck configs and will catch violations specific to that schema, unlike generic JSON diff tools that have no domain knowledge. Prefer it when you need both a structural diff (added/removed/changed paths) and schema compliance checking in a single call.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting exceeds 32 levels — rejected with depth error
- Malformed JSON input (not valid JSON) — parse error returned
- YAML or TOML input submitted instead of JSON — not supported, rejected
- Payment not received — request not processed

## How this service works

Change audit: Elgato Stream Deck: Audit JSON changes and validate before/after for Elgato Stream Deck. 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 containing JSON pointers to changed locations, lists of added/removed/changed paths, schema rule violations present before and after, newly introduced errors, and errors that were resolved by the change. Up to 100 KB per document is supported with up to 32 nesting levels.

## 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/change-audit-elgato-stream-deck-json-validator-37e838e6/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)