# Validate component-detection-manifest.json

> Validate component-detection-manifest.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 component-detection-manifest.json, reporting JSON pointer violations and rule errors.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-component-detection-manife-115a31df-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-component-detection-manifest-json-9f6952ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0J99xZNowuQGeAEFih2QB

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-component-detection-manifest-json-9f6952ec -d '<json body>'
```

Example prompt: Can you validate this component-detection-manifest.json content for me and tell me if there are any schema violations or JSON pointer errors? Here's the document: {"components": [{"name": "my-lib", "version": "1.0.0"}]}

## When to prefer this

Use this endpoint when you need to validate a component-detection-manifest.json file specifically against its pinned SchemaStore definition with precise JSON pointer–level error reporting. Prefer it over generic JSON validators when you need schema-aware validation tied to the component-detection-manifest.json spec rather than arbitrary schemas.

## 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
- SchemaStore definition unavailable or outdated — may produce incomplete validation
- Non-JSON formats (YAML, TOML) not parsed — submission fails or is treated as invalid

## How this service works

Validate component-detection-manifest.json: Validate a JSON document for component-detection-manifest.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 report indicating whether the submitted JSON document conforms to the pinned SchemaStore definition for component-detection-manifest.json, including any JSON pointer locations and 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-component-detection-manifest-json-9f6952ec/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)