# BRAINIAC JSON Schema Validate

> BRAINIAC JSON Schema Validate is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.04/call, status unknown (last checked 2026-11-17).

Validates a JSON payload against a JSON Schema and returns a structured list of validation issues with codes, paths, and details

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/api-integration/json-schema-validate?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-json-schema-validate-0b5cb4dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_S7SHDtP4StKFVda8C-24R

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 brainiac-json-schema-validate-0b5cb4dc -d '<json body>'
```

Example prompt: Can you validate this JSON payload against my schema and tell me exactly what's wrong — which fields are missing, which have the wrong type, and which are unexpected? Here's the JSON: {"id": 42, "note": "hello"} and the schema requires id to be a string, total to be present, and no additional properties.

## When to prefer this

Choose this endpoint when you need a quick, pay-per-call JSON Schema validation with no account setup, especially for one-off checks in an agentic workflow. It is well-suited for validating API request or response payloads against a known schema, detecting missing required fields, type mismatches, and additional properties. It is not suitable for schemas relying heavily on unsupported keywords (e.g. if/then/else, $ref to external URIs) or when you need code execution or external lookups during validation.

## Known failure modes

- Unsupported JSON Schema keywords are reported but not applied — results may be incomplete for complex schemas
- File payload exceeds 12MB base64 limit — request rejected
- JSON string exceeds 200,000 character limit — request rejected
- Invalid base64 encoding in file field — parsing error
- Schema references external $refs — not resolved, external calls are never made
- mediaType not in allowed enum (application/json, text/plain) — validation error
- Malformed JSON in the json field — cannot parse
- Payment not received or insufficient USDC — 402 response, no result returned

## How this service works

Pay-per-call APIs for software agents. No account. Pay the listed USDC amount on Base with x402, then receive the result.

## Output

A JSON object containing: a 'status' field ('valid' or 'invalid'), a 'checkedAt' ISO timestamp, an array of 'issues' each with a code (e.g. required_missing, type_mismatch, additional_property), a kind (missing or conflict), the JSON path where the issue occurs, a human-readable detail message, and the violated JSON Schema keyword. Also includes a 'limitations' array describing what the validator does and does not cover (e.g. supported keywords, format checks).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "file": {
   "type": "object",
   "required": [
    "mediaType",
    "fileBase64"
   ],
   "properties": {
    "filename": {
     "type": "string",
     "maxLength": 180,
     "minLength": 1
    },
    "mediaType": {
     "enum": [
      "application/json",
      "text/plain"
     ],
     "type": "string"
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "side": {
   "enum": [
    "request",
    "response"
   ],
   "type": "string"
  },
  "after": {
   "$ref": "#/$defs/__schema0"
  },
  "before": {
   "$ref": "#/$defs/__schema0"
  },
  "schema": {
   "$ref": "#/$defs/__schema0"
  },
  "source": {
   "$ref": "#/$defs/__schema0"
  },
  "target": {
   "$ref": "#/$defs/__schema0"
  },
  "example": {
   "$ref": "#/$defs/__schema0"
  },
  "payload": {
   "$ref": "#/$defs/__schema0"
  },
  "examples": {
   "type": "array",
   "items": {
    "$ref": "#/$defs/__schema0"
   },
   "maxItems": 20
  },
  "toVersion": {
   "type": "string",
   "maxLength": 40,
   "minLength": 1
  },
  "operations": {
   "type": "array",
   "items": {
    "oneOf": [
     {
      "type": "object",
      "required": [
       "op",
       "from",
       "to"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "rename"
       },
       "to": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       },
       "from": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     {
      "type": "object",
      "required": [
       "op",
       "from",
       "to"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "copy"
       },
       "to": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       },
       "from": {
        "type": "string",
        "maxLength": 200,
        "minLength": 1
       }
      },
      "additionalProperties": false
     },
     {
      "type": "object",
      "required": [
       "op",
       "paths"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "pick"
       },
       "paths": {
        "type": "array",
        "items": {
         "type": "string",
         "maxLength": 200,
         "minLength": 1
        },
        
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "issues": [
   {
    "code": "required_missing",
    "kind": "missing",
    "path": "/total",
    "detail": "This required property is absent. No value was invented.",
    "keyword": "required"
   },
   {
    "code": "type_mismatch",
    "kind": "conflict",
    "path": "/id",
    "detail": "The value is number. The schema allows string.",
    "keyword": "type"
   },
   {
    "code": "additional_property",
    "kind": "conflict",
    "path": "/note",
    "detail": "This property is not in the schema. It was not removed.",
    "keyword": "additionalProperties"
   }
  ],
  "status": "invalid",
  "checkedAt": "2026-11-03T15:00:00.000Z",
  "limitations": [
   "No external API is called and no user-supplied code is executed.",
   "Validation covers type, properties, required, additionalProperties, items, enum, const, length, range, and the formats email, date, and date-time. Other JSON Schema keywords are reported and not applied.",
   "A generated schema uses only values present in the supplied examples. additionalProperties stays true.",
   "A field mapping is proposed only when the path matches or the field name matches one field on each side.",
   "Breaking and non-breaking labels are returned only when side is request or response.",
   "Transforms are rename, copy, pick, omit, cast, and default. A default is written only when the path is absent."
  ],
  "codeExecuted": false,
  "externalCall": false,
  "valuesInvented": false,
  "schemaCompliance": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-json-schema-validate-0b5cb4dc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
