# Azure IoT Operations Connector Metadata Change Audit

> Azure IoT Operations Connector Metadata 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-18).

Validates and diffs two JSON documents representing Azure IoT Operations connector metadata, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-azure-iot-operations-conne-1f7e7f04-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/azure-iot-operations-connector-metadata-change-audit-98bedfcc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_coyGs0wID8Z0LkTrvXI9I

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 azure-iot-operations-connector-metadata-change-audit-98bedfcc -d '<json body>'
```

Example prompt: Can you audit my Azure IoT Operations connector metadata change? Here's the before document and the after document — I want to know what paths were added, removed, or changed, and whether any new schema rule violations were introduced or old ones resolved.

## When to prefer this

Use this endpoint when you specifically need to audit JSON changes to Azure IoT Operations connector metadata against a pinned SchemaStore schema definition. It is ideal for CI/CD pipelines, PR reviews, or pre-deployment checks where you want to catch schema violations and structural diffs in one call. Prefer this over generic JSON diff tools when Azure IoT Operations schema compliance is required alongside structural change detection.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — parsing fails
- Input is YAML or TOML instead of JSON — not parsed
- Malformed JSON in before or after field — validation error
- Payment not completed — endpoint returns 402
- SchemaStore definition unavailable or stale — results may not reflect latest schema

## How this service works

Change audit: Azure IoT Operations connector metadata: Audit JSON changes and validate before/after for Azure IoT Operations connector metadata. 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 diff of the two JSON documents including JSON pointers for added, removed, and changed paths, a list of schema rule violations introduced or resolved between the before and after versions, and any validation errors detected against the pinned SchemaStore definition for Azure IoT Operations connector metadata.

## 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/azure-iot-operations-connector-metadata-change-audit-98bedfcc/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)