# JSON Schema Validate

> JSON Schema Validate is a paid API for AI agents from chargers-borders-cedar-fig.trycloudflare.com, paid per call via x402, price unknown, status unknown (last checked 2026-09-15).

Validates a JSON body against a JSON Schema definition, returning validation results

## Facts

- Endpoint: POST https://chargers-borders-cedar-fig.trycloudflare.com/tools/json-schema-validate
- Price: price unknown
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/json-schema-validate-f51efd2a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2MOnAavlj0vQQ2e_hLE_A

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 json-schema-validate-f51efd2a -d '<json body>'
```

Example prompt: Can you validate this JSON body against JSON Schema — it's a POST request with a body object like {"name": "Alice", "age": 30} and I need to know if it's valid before I send it?

## When to prefer this

Use this endpoint when you need a quick, stateless JSON Schema validation check for HTTP request bodies (POST, PUT, or PATCH). It is well-suited for pre-flight validation before sending data to downstream APIs, automated CI pipeline checks, or any scenario where you need to confirm schema compliance without setting up a full validation library locally.

## Known failure modes

- Missing required 'input' field returns a 400-level error
- Missing 'type' or 'method' fields inside input causes schema rejection
- Invalid HTTP method (not POST, PUT, or PATCH) causes enum validation failure
- Malformed JSON body causes parse error
- Empty or null body object may produce unexpected validation behavior

## How this service works

opentools utility endpoint

## Output

Returns a validation outcome indicating whether the provided JSON body is valid according to JSON Schema rules, along with any specific validation errors or constraint violations found in the input.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/json-schema-validate-f51efd2a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chargers-borders-cedar-fig.trycloudflare.com](https://www.zero.xyz/host/chargers-borders-cedar-fig.trycloudflare.com/llms.txt)