# BRAINIAC API Integration Response Normalize

> BRAINIAC API Integration Response Normalize is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.03/call, status unknown (last checked 2026-11-17).

Normalizes, transforms, validates, and maps API request/response payloads between formats and versions

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/api-integration/response-normalize?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-api-integration-response-normalize-8cf1b6ab
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N-lRBHJsG0QFc3mqmu-ZL

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-api-integration-response-normalize-8cf1b6ab -d '<json body>'
```

Example prompt: Normalize this API response JSON for me — sort the keys, trim whitespace from string values, and tell me what changed: {"b": " x ", "a": 1}

## When to prefer this

Choose this endpoint when an AI agent needs to programmatically clean, reshape, validate, or migrate a JSON API payload without executing any user code or making external calls. It is especially useful when bridging two API versions, enforcing schema compliance, or preparing a payload for a downstream service that expects a specific field structure. It is not suitable for transformations requiring custom logic, external data lookups, or formats other than JSON/plain text.

## Known failure modes

- Invalid or malformed JSON input returns validation error
- Base64-encoded file exceeds 12MB limit — rejected
- Unsupported mediaType for file input — only application/json and text/plain accepted
- Unrecognized JSON Schema keywords reported but not applied — partial validation coverage
- Field mapping proposals only generated when path or field name matches — ambiguous fields may not be mapped
- 'side' field required for breaking/non-breaking labels — omitting it skips that classification
- Payload or file JSON too large (>200,000 chars for json field) — rejected

## 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

Returns a normalized JSON result object containing: the transformed payload under 'result', a 'status' field ('normalized'), a 'changes' array listing each transformation applied with path, rule, original and normalized values, an 'issues' array for validation problems, counts of changes, timestamps, and boolean flags (codeExecuted, externalCall, valuesInvented, schemaCompliance) confirming no external calls or invented values were used.

## 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": [],
  "result": {
   "a": 1,
   "b": "x"
  },
  "status": "normalized",
  "changes": [
   {
    "path": "/",
    "rule": "sort_keys",
    "original": "b,a",
    "normalized": "a,b"
   },
   {
    "path": "/b",
    "rule": "trim",
    "original": "\" x \"",
    "normalized": "\"x\""
   }
  ],
  "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."
  ],
  "changedCount": 2,
  "codeExecuted": false,
  "externalCall": false,
  "valuesInvented": false,
  "schemaCompliance": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-api-integration-response-normalize-8cf1b6ab/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)
