# Validate deployed-cli JSON Schema

> Validate deployed-cli JSON Schema 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-18).

Validates a JSON document against a pinned SchemaStore definition for deployed-cli, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-deployed-cli-1f980e02-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-deployed-cli-json-schema-53fc9c62
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Iv0Q7lu1GdDnxgeXq-GDT

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-deployed-cli-json-schema-53fc9c62 -d '<json body>'
```

Example prompt: Can you validate this deployed-cli JSON config for me and tell me if there are any schema violations or JSON pointer errors? Here's the document: {"name":"my-deployment","version":"1.0.0"}

## When to prefer this

Choose this endpoint when you specifically need to validate a JSON document against the deployed-cli schema from SchemaStore, especially when you need precise JSON pointer paths for violations rather than a generic JSON linter. It is ideal for CI/CD preflight checks, developer tooling pipelines, and configuration auditing workflows where deployed-cli compliance is required. Not suitable for YAML/TOML configs, general-purpose JSON schema validation against arbitrary schemas, or deployment execution guarantees.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- Nesting depth exceeds 32 levels — validation refused
- Input is not valid JSON (e.g. YAML or TOML) — parse error returned
- Missing or empty 'document' field — validation cannot proceed
- Schema definition unavailable or pinned schema mismatch — internal error

## How this service works

Validate deployed-cli: Validate a JSON document for deployed-cli. 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 structured report indicating whether the JSON document is valid against the pinned deployed-cli SchemaStore definition, listing any JSON pointer paths that violate schema rules along with the specific rule violations encountered. Documents up to 100 KB and 32 nesting levels are accepted.

## 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-deployed-cli-json-schema-53fc9c62/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)