# Busker JSON Schema Validator

> Busker JSON Schema Validator is a paid API for AI agents from workbot1.oddsys.org, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-11).

Validates one or up to 100 JSON instances against a JSON Schema (draft-07, 2019-09, 2020-12) returning all violations with path, keyword, and message

## Facts

- Endpoint: POST https://workbot1.oddsys.org/validate?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/busker-json-schema-validator-2104b793
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7zASelrVUPo5QnDdebBLp

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 busker-json-schema-validator-2104b793 -d '<json body>'
```

Example prompt: Check this JSON object against my schema and list every violation with its path and keyword — I need to know exactly which fields fail and why, including string format errors.

## When to prefer this

Choose this endpoint when you need detailed, per-violation structured feedback (path + keyword + message) for JSON Schema validation across draft-07, 2019-09, or 2020-12, especially when you need string format validation or batch validation of up to 100 instances in a single call. Prefer it over client-side validators when running in an agent environment without a local runtime, or when you need normalized, machine-readable violation objects rather than a simple pass/fail.

## Known failure modes

- Remote $ref in schema is rejected — the schema must be self-contained
- More than 100 instances in the items array returns an error
- Malformed JSON in dataText field is reported as a parse-error violation rather than a hard failure
- Invalid or unrecognized $schema draft URI may fall back to draft-07 or return an error
- Passing both data and items simultaneously may cause ambiguous behavior

## How this service works

Validate JSON against a JSON Schema (draft-07, 2019-09, 2020-12, with string formats): every violation with path, keyword and message. One instance, a JSON string, or up to 100 instances against one schema.

## Output

A list of all schema violations found, each containing the JSON path to the offending value, the schema keyword that was violated (e.g. 'type', 'required', 'format'), and a human-readable message explaining the violation. Returns an empty violations list if the instance is fully valid. For batch calls, violations are grouped or indexed per instance.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "description": "The instance to validate (any JSON value)."
  },
  "items": {
   "type": "array",
   "maxItems": 100,
   "description": "Validate many instances against the one schema."
  },
  "schema": {
   "type": "object",
   "description": "JSON Schema (draft-07 default; $schema may select 2019-09 or 2020-12). Remote $ref is rejected."
  },
  "dataText": {
   "type": "string",
   "description": "The instance as a JSON string (parsed first; parse errors are reported as a violation)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/busker-json-schema-validator-2104b793/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from workbot1.oddsys.org](https://www.zero.xyz/host/workbot1.oddsys.org/llms.txt)