# MetricsHub Configuration Change Auditor

> MetricsHub Configuration Change Auditor 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).

Audits JSON changes between before/after MetricsHub Configuration documents, reporting added/removed/changed paths and schema rule violations using a pinned SchemaStore definition.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-metricshub-configuration-e9e49bda-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/metricshub-configuration-change-auditor-100f1d4b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JZFX1QwnMoyuJyOdKMGNF

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 metricshub-configuration-change-auditor-100f1d4b -d '<json body>'
```

Example prompt: Can you audit the change I just made to my MetricsHub configuration — 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 or old ones resolved?

## When to prefer this

Choose this endpoint when you specifically need to validate and diff MetricsHub Configuration JSON documents against a pinned SchemaStore schema. It is purpose-built for MetricsHub configuration change auditing with precise JSON pointer reporting, making it preferable to generic JSON diff tools when schema compliance and error tracking across a before/after pair matter. Not suitable for YAML/TOML configs, non-MetricsHub schemas, or documents over 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (non-parseable) — error returned
- YAML or TOML input not supported — must convert to JSON first
- Network or payment failure — no audit result returned

## How this service works

Change audit: MetricsHub Configuration: Audit JSON changes and validate before/after for MetricsHub Configuration. 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 of JSON pointer-level differences between the before and after MetricsHub Configuration documents, including lists of added, removed, and changed paths, schema rule violations present in each document, and which errors were introduced or resolved by the change. Uses a pinned SchemaStore definition for validation. Documents up to 100 KB and 32 nesting levels are supported.

## 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/metricshub-configuration-change-auditor-100f1d4b/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)