# BRAINIAC JSON Schema Validator

> BRAINIAC JSON Schema Validator 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-12).

Validates a JSON payload against a JSON Schema and returns detailed per-field validation issues with codes, paths, and descriptions

## Facts

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

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-validator-2b9c13f1 -d '<json body>'
```

Example prompt: Can you validate this JSON payload against my schema and tell me exactly which fields are missing, have the wrong type, or aren't allowed? Here's the JSON: {"id": 42, "note": "hello"} and the schema requires 'total' as a string and forbids additional properties.

## When to prefer this

Choose this endpoint when you need fast, deterministic, pay-per-call JSON Schema validation with no account setup, no code execution, and no external calls — ideal for agents validating API request/response payloads before or after transmission. Prefer it over heavyweight validation libraries when running in a serverless or agent context where spinning up a JSON Schema engine is impractical, or when you need structured machine-readable issue reports with per-field codes and paths.

## Known failure modes

- Unsupported JSON Schema keywords (e.g. $ref resolution, if/then/else) are reported but not enforced
- Validation only covers type, properties, required, additionalProperties, items, enum, const, length, range, email/date/date-time formats — other keywords are noted as not applied
- Breaking/non-breaking change labels are only returned when 'side' is set to 'request' or 'response'
- Oversized payloads (json > 200,000 chars or file base64 > 12,000,000 chars) will be rejected
- Malformed base64 file input will cause a parse error
- Field mappings are only proposed when path or field name matches one field on each side

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object with a 'status' field ('valid' or 'invalid'), a 'checkedAt' timestamp, an 'issues' array where each item contains a code (e.g. 'required_missing', 'type_mismatch', 'additional_property'), a 'kind' ('missing' or 'conflict'), a JSON pointer 'path', a human-readable 'detail', and the offending JSON Schema 'keyword'. Also includes a 'limitations' array listing unsupported keywords and behavioral constraints, plus boolean flags: codeExecuted, externalCall, valuesInvented, schemaCompliance.

## 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": {},
  "before": {},
  "schema": {},
  "source": {},
  "target": {},
  "example": {},
  "payload": {},
  "examples": {
   "type": "array",
   "items": {},
   "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
        },
        "maxItems": 40,
        "minItems": 1
       }
      },
      "additionalProperties": false
     },
     {
      "type": "object",
      "required": [
       "op",
       "paths"
      ],
      "properties": {
       "op": {
        "type": "string",
        "const": "omit"
… (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-validator-2b9c13f1/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)
