# Validate Dust Configuration

> Validate Dust Configuration 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).

Validates a JSON document against a pinned SchemaStore definition for Dust configuration, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-dust-configuration-3a742aab-validate?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/validate-dust-configuration-66b44f8d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Vud5P37MRBBMLrK2BVNLL

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 validate-dust-configuration-66b44f8d -d '<json body>'
```

Example prompt: Can you validate this Dust configuration JSON for me and tell me if there are any schema violations or JSON pointer errors?

## When to prefer this

Choose this endpoint when you specifically need to validate a JSON document against the Dust configuration schema using a pinned SchemaStore definition. It is ideal for CI/CD pipelines, pre-deployment checks, or debugging Dust agent configurations. It does not support YAML or TOML formats, and does not provide deployment or security guarantees — use it purely for schema compliance checking.

## Known failure modes

- Document exceeds 100 KB size limit — rejected with size error
- Nesting depth exceeds 32 levels — rejected with depth error
- Input is not valid JSON at all — parse error returned before schema validation
- Schema store definition unavailable or stale — may produce outdated validation results
- Empty or null document submitted — may return schema mismatch errors

## How this service works

Validate Dust configuration: Validate a JSON document for Dust configuration. Uses a pinned SchemaStore definition on this PC. Reports JSON pointers and rule violations. Up to 100 KB per document; no YAML/TOML parsing or deployment/security guarantee. 0.01 USDC includes one JSON document validation.

## Output

Returns a validation report indicating whether the JSON document conforms to the pinned Dust configuration SchemaStore definition, including a list of JSON pointer paths where violations occur and descriptions of each rule violation found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "document": {
   "default": {},
   "description": "JSON value to validate; maximum 100 KB, 32 levels."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/validate-dust-configuration-66b44f8d/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)