# Dust Configuration Change Auditor

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

Audits JSON diff between before/after Dust 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-dust-configuration-3a742aab-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/dust-configuration-change-auditor-0a89fdfc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gOX_tP5nUPQAT4gwIAFuJ

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 dust-configuration-change-auditor-0a89fdfc -d '<json body>'
```

Example prompt: Can you audit my Dust configuration change? Here's the before config: {} and after config: {"agent_market_example": true} — tell me what paths were added, removed, or changed, and flag any schema rule violations that were introduced or resolved.

## When to prefer this

Choose this endpoint when you specifically need to audit changes to a Dust configuration JSON file against its SchemaStore definition, and want a structured diff of added/removed/changed paths with introduced/resolved schema violations. Prefer it over generic JSON diff tools when Dust-specific schema rule enforcement is needed, and over full deployment pipelines when you only need a lightweight pre-commit or PR validation step.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — parsing error
- Malformed JSON input for before or after — parse failure
- Invalid or non-Dust-configuration JSON structure — schema mismatch reported
- Payment not received — 402 response, audit not performed

## How this service works

Change audit: Dust configuration: Audit JSON changes and validate before/after for Dust 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

A structured report listing JSON pointers for all added, removed, and changed paths between the before and after Dust configuration documents, along with schema rule violations that were introduced or resolved, based on a pinned SchemaStore definition. Does not include YAML/TOML parsing or deployment/security guarantees.

## 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/dust-configuration-change-auditor-0a89fdfc/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)