# Validate dotnetcli.host.json

> Validate dotnetcli.host.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-15).

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

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-dotnetcli-host-json-fc081f18-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-dotnetcli-host-json-b45c5be2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sB8di8RHbkeSG_FON4eq3

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-dotnetcli-host-json-b45c5be2 -d '<json body>'
```

Example prompt: Can you validate this dotnetcli.host.json document 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 dotnetcli.host.json configuration file against its official SchemaStore definition. It uses a pinned schema version for reproducible results and reports precise JSON pointer paths for each violation, making it ideal for CI pipelines, developer tooling, or automated checks. Prefer this over generic JSON validators when dotnetcli host configuration correctness is required.

## Known failure modes

- Document exceeds 100 KB limit — request rejected
- JSON nesting exceeds 32 levels — validation refused
- Malformed JSON input (not parseable) — error returned
- Schema definition unavailable or pinned version mismatch — validation may fail unexpectedly
- Non-JSON formats (YAML, TOML) are not supported and will fail

## How this service works

Validate dotnetcli.host.json: Validate a JSON document for dotnetcli.host.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 structured validation result indicating whether the JSON document conforms to the pinned SchemaStore schema for dotnetcli.host.json, including a list of JSON pointer paths where violations occur and descriptions of the specific rule violations 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-dotnetcli-host-json-b45c5be2/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)