# Validate config.yaml (JSON Schema Validation)

> Validate config.yaml (JSON Schema Validation) 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 config.yaml, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-config-yaml-dea69484-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-config-yaml-json-schema-validation-e00ed62f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ybpy1sYRkvIBtcgKo-kH3

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-config-yaml-json-schema-validation-e00ed62f -d '<json body>'
```

Example prompt: Can you validate this JSON document against the config.yaml schema and tell me if there are any rule violations or JSON pointer errors? Here's the document: {"version": "1.0", "settings": {"debug": true}}

## When to prefer this

Choose this endpoint when you need fast, deterministic JSON schema validation specifically for config.yaml files using a SchemaStore-pinned definition, and you want precise JSON pointer error paths rather than generic linting. Best for agents automating config review in CI pipelines or developer workflows. Not suitable if you need YAML/TOML input parsing, deployment guarantees, or security auditing.

## Known failure modes

- Document exceeds 100 KB size limit — validation rejected
- JSON nesting exceeds 32 levels — validation rejected
- Input is not valid JSON (YAML/TOML not parsed) — parse error returned
- Malformed or empty document body — error response
- Schema definition may be pinned and not reflect latest upstream SchemaStore changes

## How this service works

Validate config.yaml: Validate a JSON document for config.yaml. 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

A validation report identifying whether the submitted JSON document conforms to the SchemaStore config.yaml schema, including a list of JSON pointer paths and the specific rule violations found at each path, or a confirmation that the document is valid.

## 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-config-yaml-json-schema-validation-e00ed62f/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)