# apex-edge JSON Validate

> apex-edge JSON Validate is a paid API for AI agents from apex-edge.pearceshrader.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-10).

Validates whether a submitted payload is well-formed JSON, returning a structured validation result

## Facts

- Endpoint: GET https://apex-edge.pearceshrader.workers.dev/api/v1/util/json-validate?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apex-edge-json-validate-0ac0fb3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_AiYLUoXi5qR3RoiZ0u7nF

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 apex-edge-json-validate-0ac0fb3a
```

Example prompt: Can you check whether this string is valid JSON for me: '{"name":"Alice","age":30,"active":true}'?

## When to prefer this

Choose this endpoint when you need a lightweight, pay-per-call JSON syntax validation check without standing up your own parser or validator, especially within an x402-payment-enabled agentic workflow where micro-cost API calls are acceptable

## Known failure modes

- Empty body submitted — returns validation error or 400
- Non-JSON content type mismatch causing parse failure before validation
- Oversized payload exceeding worker request limits — returns 413 or timeout
- Payment not included or insufficient — returns 402 Payment Required
- Malformed request envelope (not the JSON being tested) — may return 400

## How this service works

x402-paid inference + audit endpoints

## Output

Returns a JSON object indicating whether the submitted payload is valid JSON, along with error details such as position and description of any syntax issues if validation fails

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "queryParams": {
     "type": "object",
     "properties": {
      "input": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "example": {
     "status": "ok"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apex-edge-json-validate-0ac0fb3a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from apex-edge.pearceshrader.workers.dev](https://www.zero.xyz/host/apex-edge.pearceshrader.workers.dev/llms.txt)