# BRAINIAC Executable Metadata Analyzer

> BRAINIAC Executable Metadata Analyzer 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).

Performs static analysis of executable file metadata to detect risk indicators such as packing, obfuscation, or structural anomalies — without executing the file or contacting external scanners.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/file-security/executable-metadata-analyze?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-executable-metadata-analyzer-58f1f1d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xJ-_Uxyp6WO8Dl_ty5UHY

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-executable-metadata-analyzer-58f1f1d1 -d '<json body>'
```

Example prompt: Can you statically analyze this Windows executable for me — I'll give you the base64 of the file and its filename 'installer.exe' — and tell me if there are any suspicious PE header anomalies, packing indicators, or structural red flags without actually running it?

## When to prefer this

Choose this endpoint when you need fast, privacy-preserving static analysis of executable files without sending data to external threat-intel services, executing the binary, or requiring an API key. Ideal for CI/CD pipelines, incident response triage, or agent workflows that must assess executable risk locally and transparently. Not suitable when you need dynamic behavioral analysis, sandbox execution, or confirmed malware verdict from a threat-intel database.

## Known failure modes

- Insufficient file bytes provided — PE header cannot be fully parsed (pe_header_incomplete status)
- File base64 too large — exceeds 12MB decoded size limit
- Unsupported file type — non-executable media types may yield no meaningful findings
- Archive depth or entry count limits exceeded — nested archives may not be fully inspected
- No findings returned when file lacks executable signatures — does not confirm file is clean

## 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 structured JSON report with: an array of items each with a title, status, confidence level, observed facts, inferred threats, and whether confirmed malware was found; a top-level status; a findings array with coded risk findings; a checkedAt timestamp; and explicit limitations clarifying that files are never executed, no external scanners are used, and absence of findings is not a malware-free guarantee.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "csv": {
   "type": "string",
   "maxLength": 200000
  },
  "asOf": {
   "type": "string",
   "maxLength": 40
  },
  "file": {
   "type": "object",
   "properties": {
    "id": {
     "type": "string",
     "maxLength": 80
    },
    "md5": {
     "type": "string",
     "maxLength": 64
    },
    "role": {
     "type": "string",
     "maxLength": 80
    },
    "sha1": {
     "type": "string",
     "maxLength": 80
    },
    "sha256": {
     "type": "string",
     "maxLength": 128
    },
    "source": {
     "type": "string",
     "maxLength": 200
    },
    "filename": {
     "type": "string",
     "maxLength": 260,
     "minLength": 1
    },
    "mediaType": {
     "type": "string",
     "maxLength": 120
    },
    "sizeBytes": {
     "type": "number",
     "maximum": 100000000,
     "minimum": 0
    },
    "fileBase64": {
     "type": "string",
     "maxLength": 12000000,
     "minLength": 1
    }
   },
   "additionalProperties": false
  },
  "json": {
   "type": "string",
   "maxLength": 200000
  },
  "text": {
   "type": "string",
   "maxLength": 200000
  },
  "files": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "md5": {
      "type": "string",
      "maxLength": 64
     },
     "role": {
      "type": "string",
      "maxLength": 80
     },
     "sha1": {
      "type": "string",
      "maxLength": 80
     },
     "sha256": {
      "type": "string",
      "maxLength": 128
     },
     "source": {
      "type": "string",
      "maxLength": 200
     },
     "filename": {
      "type": "string",
      "maxLength": 260,
      "minLength": 1
     },
     "mediaType": {
      "type": "string",
      "maxLength": 120
     },
     "sizeBytes": {
      "type": "number",
      "maximum": 100000000,
      "minimum": 0
     },
     "fileBase64": {
      "type": "string",
      "maxLength": 12000000,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 40
  },
  "reports": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "text"
    ],
    "properties": {
     "id": {
      "type": "string",
      "maxLength": 80
     },
     "text": {
      "type": "string",
      "maxLength": 200000
     },
     "title": {
      "type": "string",
      "maxLength": 200
     },
     "source": {
      "type": "string",
      "maxLength": 200
     }
    },
    "additionalP
… (truncated)
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "items": [
   {
    "id": "exe-meta-E1",
    "title": "Executable metadata risk indicators",
    "source": "Caller-supplied",
    "status": "insufficient_evidence",
    "reasons": [
     "pe_header_incomplete"
    ],
    "detector": "executable-metadata-analyze",
    "evidence": [
     {
      "fact": "magic=pe_executable; sizeBytes=11; MZ found but PE header could not be fully parsed within supplied bytes.",
      "subject": "E1",
      "inference": "Static metadata only; file was not executed.",
      "confidence": "low"
     }
    ],
    "confidence": "low",
    "relatedIds": [
     "E1"
    ],
    "observedFacts": [
     "magic=pe_executable",
     "sizeBytes=11",
     "MZ found but PE header could not be fully parsed within supplied bytes."
    ],
    "inferredThreat": "Executable structural features can indicate packing or disguise.",
    "confirmedMalware": false
   }
  ],
  "status": "analyzed",
  "findings": [
   {
    "code": "executable_metadata",
    "kind": "conflict",
    "detail": "Executable indicators: pe_header_incomplete (confirmedMalware=false).",
    "subject": "E1"
   }
  ],
  "checkedAt": "2026-11-04T21:00:00.000Z",
  "itemCount": 1,
  "limitations": [
   "Files and analysis reports are copied only from caller-supplied fields. Uploaded bytes are never executed and are never sent to external malware scanners.",
   "Analysis is static/local only with strict decoded-size, archive-depth, entry-count, and decompression limits.",
   "Observed facts are separated from inferred threat hypotheses. Absence of matched patterns is not a malware-free verdict.",
   "Nested archive inspection lists metadata and may inflate only small members within decompression caps.",
   "No paid threat-intel feed is used and no API key is required."
  ],
  "fileExecuted": false,
  "apiKeyRequired": false,
  "networkAccessed": false,
  "paidProviderUsed": false,
  "externalScannerUsed": false,
  "malwareFreeNotClaimed": true,
  "confirmedMalwareClaimed": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-executable-metadata-analyzer-58f1f1d1/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)
