# BRAINIAC KEV Exposure Check

> BRAINIAC KEV Exposure Check is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.06/call, status unknown (last checked 2026-11-17).

Checks software components or an SBOM against CISA's Known Exploited Vulnerabilities (KEV) catalog using OSV data to identify actively exploited CVEs

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/software-security/kev-exposure-check?utm_source=zero.xyz
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-kev-exposure-check-4b78f5e9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-jqW0h0a9QqtvKP4j20GP

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-kev-exposure-check-4b78f5e9 -d '<json body>'
```

Example prompt: Check these Maven components for known exploited vulnerabilities: org.apache.logging.log4j:log4j-core version 2.14.1 and commons-text:commons-text version 1.9 — I want to know if any are in the CISA KEV catalog and whether there's known ransomware associated.

## When to prefer this

Use this endpoint when you need to specifically check whether software components are listed in CISA's Known Exploited Vulnerabilities (KEV) catalog — meaning they are actively exploited in the wild, not just theoretically vulnerable. Prefer this over generic CVE scanners when the question is 'is this being actively exploited?' or 'does this have ransomware associations?' It is particularly valuable in CI/CD pipelines as a release gate, in incident triage when a specific CVE is in the news, or for compliance reporting that requires KEV coverage. It supports both structured component lists and raw SBOM inputs, making it flexible for both automated pipelines and ad-hoc checks.

## Known failure modes

- Input contains more than 25 components — only first 25 are checked, with a warning in the response
- Component purl or version is malformed — may result in no matches or lookup failure
- SBOM format not parseable — could result in zero components extracted
- OSV upstream source unavailable — source status will show error, partial results returned
- A KEV entry is only reported when an advisory for the exact package also carries the CVE ID — indirect or alias CVEs may be missed

## 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 exposures where each entry includes the component name, version, CVE ID, vulnerability name, date it was added to the KEV catalog, ecosystem, advisory ID, version status (affected/unaffected), and whether it has known ransomware associations. Also includes metadata like the catalog version and release date, a list of data sources queried with their status, any warnings (e.g. truncation at 25 components), limitations, 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": [
   "Only the first 25 components were checked."
  ],
  "exposures": [
   {
    "name": "org.apache.logging.log4j:log4j-core",
    "cveId": "CVE-2021-44228",
    "version": "2.14.1",
    "dateAdded": "2021-12-10",
    "ecosystem": "Maven",
    "advisoryId": "GHSA-jfh8-c2jp-5v3q",
    "versionStatus": "affected",
    "knownRansomware": "Known",
    "vulnerabilityName": "Apache Log4j2 Remote Code Execution Vulnerability"
   }
  ],
  "truncated": false,
  "limitations": [
   "A KEV entry is reported only when an advisory for the exact package also carries that CVE id."
  ],
  "retrievedAt": "2026-11-02T18:00:00.000Z",
  "catalogVersion": "2026.11.02",
  "approvesRelease": false,
  "catalogReleasedAt": "2026-11-02T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-kev-exposure-check-4b78f5e9/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)
