# openHAB JSON Change Audit

> openHAB 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-15).

Audits before/after JSON document pairs against the openHAB schema, reporting added, removed, and changed paths plus introduced and resolved validation errors.

## Facts

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

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 openhab-json-change-audit-acbc56f0 -d '<json body>'
```

Example prompt: Can you audit my openHAB configuration change — here's the before JSON and the after JSON — and tell me what paths were added, removed, or changed, and whether any new schema violations were introduced?

## When to prefer this

Choose this endpoint when you specifically need to validate openHAB JSON configurations against the SchemaStore definition and want a structured diff of what changed between two versions, including which changes introduced or resolved schema violations. It is purpose-built for openHAB and uses a pinned schema, making it more reliable for that domain than a generic JSON diff or validator. Prefer it over generic JSON schema validators when openHAB-specific rule coverage matters.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON in before or after field — parse error returned
- YAML or TOML input instead of JSON — not supported, error returned
- Network or payment processing failure — no result returned

## How this service works

Change audit: openHAB: Audit JSON changes and validate before/after for openHAB. 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 report listing JSON pointer paths that were added, removed, or changed between the before and after documents, along with any schema rule violations that were introduced or resolved, based on the pinned SchemaStore openHAB definition. Each entry references the relevant JSON pointer and describes the violation or change type.

## 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/openhab-json-change-audit-acbc56f0/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)