# Validate debugsettings.json

> Validate debugsettings.json 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-14).

Validates a JSON document against the pinned SchemaStore schema definition for debugsettings.json, reporting JSON pointer paths and rule violations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-debugsettings-json-4406b9b1-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-debugsettings-json-dff1a3b0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f_ecZ5mZ6HpUhbKpWz6yn

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-debugsettings-json-dff1a3b0 -d '<json body>'
```

Example prompt: Can you check this debugsettings.json content for me and tell me if it's valid? Here's the JSON: {"version":"0.2.0","configurations":[{"type":"node","request":"launch","name":"Launch Program"}]}

## When to prefer this

Choose this endpoint when you specifically need to validate a debugsettings.json file against its canonical SchemaStore definition. It is purpose-built for this schema rather than being a generic JSON Schema validator, so it provides precise, schema-aware error messages with JSON pointer paths. Prefer it over general-purpose validators when you want guaranteed schema fidelity using a pinned definition, and when the document is under 100 KB.

## Known failure modes

- Document exceeds 100 KB limit — validation rejected
- Nesting depth exceeds 32 levels — validation rejected
- Malformed JSON submitted (not parseable) — parse error returned
- Schema definition unavailable or stale on server — service error
- Input is YAML or TOML instead of JSON — not supported, error returned

## How this service works

Validate debugsettings.json: Validate a JSON document for debugsettings.json. 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 result indicating whether the supplied JSON document conforms to the pinned SchemaStore definition for debugsettings.json. On failure, includes JSON pointer paths identifying the location of each violation and a description of the rule that was broken. On success, confirms 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-debugsettings-json-dff1a3b0/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)