# Validate launchsettings.json

> Validate launchsettings.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 definition for launchsettings.json, reporting JSON pointer paths and rule violations

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-launchsettings-json-da9ea985-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-launchsettings-json-4a1c6c75
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QOsZ0tWOn2cOUD7QZra2x

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-launchsettings-json-4a1c6c75 -d '<json body>'
```

Example prompt: Can you validate this launchsettings.json document for me and tell me which fields or sections are invalid according to the schema? Here's the JSON: { "profiles": { "MyApp": { "commandName": "Project", "launchBrowser": true } } }

## When to prefer this

Choose this endpoint when you specifically need to validate a launchsettings.json configuration file used by .NET/ASP.NET projects against the SchemaStore-pinned schema. It is purpose-built for this file type and returns precise JSON pointer paths to violations, making it more useful than a generic JSON validator when the schema is launchsettings.json specifically.

## Known failure modes

- Document exceeds 100 KB limit — rejected with size error
- JSON nesting depth exceeds 32 levels — rejected
- Malformed JSON submitted (not parseable) — parse error returned
- Empty or null document — may return schema violation or trivial result
- Schema definition unavailable or outdated on the server — may produce unexpected results

## How this service works

Validate launchsettings.json: Validate a JSON document for launchsettings.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

A structured response indicating whether the submitted JSON document is valid against the pinned SchemaStore launchsettings.json schema, including a list of JSON pointer paths for each rule violation found, or 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-launchsettings-json-4a1c6c75/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)