# Validate project-1.0.0-beta3.json

> Validate project-1.0.0-beta3.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-19).

Validates a JSON document against the pinned SchemaStore definition for project-1.0.0-beta3.json, reporting any rule violations and JSON pointer locations.

## Facts

- Endpoint: POST https://market.datapackvibe.com/x402/assistant-schema-project-1-0-0-beta3-json-461922c4-validate?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/validate-project-1-0-0-beta3-json-6b96d6f2
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mAY0LYOM_16qBAAS-8yD6

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-project-1-0-0-beta3-json-6b96d6f2 -d '<json body>'
```

Example prompt: Can you validate this project.json document for me against the project-1.0.0-beta3 schema and tell me which fields are invalid or missing?

## When to prefer this

Choose this endpoint when you need to validate a JSON document specifically against the project-1.0.0-beta3.json SchemaStore schema with pinned, reproducible results. It is ideal for CI/CD pipelines, build tooling, or developer agents that need authoritative schema compliance checks without managing local schema tooling. Prefer this over generic JSON validators when the target schema is specifically project-1.0.0-beta3.json.

## Known failure modes

- Document exceeds 100 KB size limit — rejected with size error
- JSON nesting depth exceeds 32 levels — rejected with depth error
- Malformed JSON submitted (not parseable) — returns parse error
- YAML or TOML input provided instead of JSON — not supported, returns format error
- Empty or null document body — may return schema violation or empty result

## How this service works

Validate project-1.0.0-beta3.json: Validate a JSON document for project-1.0.0-beta3.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 report indicating whether the submitted JSON document conforms to the project-1.0.0-beta3.json SchemaStore definition, including a list of rule violations and their exact JSON pointer locations within the document.

## 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-project-1-0-0-beta3-json-6b96d6f2/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)