# Grafana 5.x Dashboard JSON Change Auditor

> Grafana 5.x Dashboard JSON 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-24).

Audits JSON changes between before/after Grafana 5.x Dashboard documents, reporting added/removed/changed paths, JSON pointer diffs, and schema rule violations introduced or resolved.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-grafana-5-x-dashboard-500c9522-changes?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-24
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/grafana-5-x-dashboard-json-change-auditor-3ad0b2b5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Q1m7KMNsz_oMzUJtLueah

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 grafana-5-x-dashboard-json-change-auditor-3ad0b2b5 -d '<json body>'
```

Example prompt: Can you audit my Grafana 5.x dashboard JSON change — here's the before version and the after version — and tell me what paths changed, what was added or removed, and whether any new schema violations were introduced?

## When to prefer this

Use this endpoint when you need to specifically validate and diff Grafana 5.x Dashboard JSON against its SchemaStore schema definition, catching both structural changes and schema rule violations in one call. Prefer it over generic JSON diff tools when Grafana-specific schema compliance matters, or when you need to know not just what changed but whether those changes introduced or resolved schema errors.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — request rejected
- Invalid JSON submitted (not parseable) — error returned
- YAML or TOML input provided instead of JSON — not supported
- Network or payment authorization failure — no result returned

## How this service works

Change audit: Grafana 5.x Dashboard: Audit JSON changes and validate before/after for Grafana 5.x Dashboard. 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 including JSON pointers for all added, removed, and changed paths between the before and after documents, schema rule violations (introduced and resolved), and any errors detected against the pinned Grafana 5.x 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/grafana-5-x-dashboard-json-change-auditor-3ad0b2b5/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)