# BRAINIAC SBOM Vulnerability Match

> BRAINIAC SBOM Vulnerability Match is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.08/call, status unknown (last checked 2026-11-17).

Matches software components from an SBOM or component list against known vulnerability advisories using OSV and similar public sources

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/software-security/sbom-vulnerability-match?utm_source=zero.xyz
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-sbom-vulnerability-match-9bf2f41e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oT3O9cA-gbwWHfk6F3Acf

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-sbom-vulnerability-match-9bf2f41e -d '<json body>'
```

Example prompt: Can you check if my Maven component org.apache.logging.log4j:log4j-core version 2.14.1 has any known vulnerabilities or CVEs? Use the SBOM vulnerability matcher.

## When to prefer this

Use this endpoint when you need a fast, accountless, pay-per-call vulnerability check against public advisory databases (primarily OSV) for specific software components or an SBOM. Prefer this over full SAST/DAST tools when you have structured component metadata (name, version, ecosystem, purl) and want targeted CVE/advisory matching without integrating a heavyweight security scanning platform. Best suited for CI/CD pipeline checks, vendor SBOM audits, or agent-driven compliance workflows.

## Known failure modes

- Exact version/name matching required — fuzzy or approximate package names will not match
- Missing or malformed purl may result in no matches even for vulnerable packages
- Advisory databases may lag behind newly disclosed CVEs, producing false negatives
- Component ecosystem mismatch (e.g. wrong ecosystem string) causes missed matches
- Input exceeds 25 component limit or SBOM character limit returns validation error
- Network or upstream OSV API unavailability returns source error with status field

## 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 list of matched components, each with associated vulnerability advisories including CVE/GHSA IDs, severity (CVSS scores), affected status, summary descriptions, and modification dates. Also includes data source metadata (e.g. OSV), retrieval timestamps, any warnings about truncated or omitted advisories, and an overall approvesRelease boolean flag.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "sbom": {
   "type": "string",
   "maxLength": 400000,
   "minLength": 2
  },
  "components": {
   "type": "array",
   "items": {
    "type": "object",
    "properties": {
     "name": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "purl": {
      "type": "string",
      "maxLength": 500,
      "minLength": 4
     },
     "license": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1
     },
     "version": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1
     },
     "ecosystem": {
      "type": "string",
      "maxLength": 40,
      "minLength": 1
     }
    },
    "additionalProperties": false
   },
   "maxItems": 25,
   "minItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "sources": [
   {
    "url": "https://api.osv.dev/v1/querybatch",
    "detail": "Public source response.",
    "source": "OSV",
    "status": "ok",
    "retrievedAt": "2026-11-02T18:00:00.000Z"
   }
  ],
  "warnings": [
   "4 advisories were not read."
  ],
  "truncated": false,
  "components": [
   {
    "name": "org.apache.logging.log4j:log4j-core",
    "purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1",
    "problem": null,
    "version": "2.14.1",
    "ecosystem": "Maven",
    "advisories": [
     {
      "id": "GHSA-jfh8-c2jp-5v3q",
      "status": "affected",
      "aliases": [
       "CVE-2021-44228"
      ],
      "summary": "Remote code execution in Log4j",
      "modified": "2021-12-18T00:00:00Z",
      "severity": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
      "malicious": false
     }
    ],
    "advisoriesOmitted": 0
   }
  ],
  "limitations": [
   "Matching uses the exact ecosystem, package name, and exact version. A similar package name is not a match."
  ],
  "retrievedAt": "2026-11-02T18:00:00.000Z",
  "approvesRelease": false
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-sbom-vulnerability-match-9bf2f41e/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)
