# MetricsHub Connector Configuration Change Audit

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

Audits JSON changes between before/after MetricsHub Connector Configuration documents, validating both against a pinned SchemaStore definition and reporting added/removed/changed paths, JSON pointer violations, and introduced/resolved errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-metricshub-connector-confi-f15ad4da-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-connector-configuration-change-audit-055fafa1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aquRLfhgcwPaSFpAdf80o

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-connector-configuration-change-audit-055fafa1 -d '<json body>'
```

Example prompt: Can you audit the change I made to my MetricsHub connector configuration — here's the before JSON and the after JSON — and tell me what paths changed, any schema violations that were introduced or resolved, and whether the new version is valid?

## When to prefer this

Use this endpoint when you specifically need to audit changes to MetricsHub Connector Configuration files, validating both before and after states against the SchemaStore-pinned schema. Prefer this over generic JSON diff tools when you need schema-aware validation, JSON pointer reporting, and explicit tracking of introduced vs resolved errors in the MetricsHub connector config domain.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Malformed JSON submitted as before or after — parse error returned
- YAML or TOML input provided instead of JSON — not supported
- SchemaStore definition unavailable or stale — validation may be incomplete

## How this service works

Change audit: MetricsHub Connector Configuration: Audit JSON changes and validate before/after for MetricsHub Connector 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 diff of the two MetricsHub Connector Configuration JSON documents, including JSON pointers to added, removed, and changed paths; schema rule violations present in before and/or after; newly introduced errors; and errors that were resolved by the change. Both documents are validated against a pinned 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/metricshub-connector-configuration-change-audit-055fafa1/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)