Check KEV exposure API
Compare exact dependency versions with OSV advisories and the CISA Known Exploited Vulnerabilities catalog. A KEV entry is reported only when that CVE applies to the same package and version range.
The Check KEV exposure operation is part of the Software Supply Chain Security API on BRAINIAC.software. Compare exact dependency versions with OSV advisories and the CISA Known Exploited Vulnerabilities catalog. A KEV entry is reported only when that CVE applies to the same package and version range. It is exposed as POST /api/v1/software-security/kev-exposure-check and priced at $0.06 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: OSV public API (api.osv.dev). CISA Known Exploited Vulnerabilities catalog JSON feed. Public npm, PyPI, crates.io, and RubyGems package records for licence identifiers. Limitations: CycloneDX and SPDX JSON are accepted, with a limited XML read of the same fields. Only an exact ecosystem, package name, and version is matched. Similar names are ignored. Affected, unaffected, and unknown version ranges are reported separately. At most 25 components and 40 advisory documents are read per call. Absence of an advisory does not mean a dependency is safe or free of malware. Licence compatibility is judged only against the caller allow and deny lists. EPSS, NVD, deps.dev, and Scorecard are not used by this product. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Match SBOM vulnerabilities, Report dependency risk, Check licence compatibility, Check malicious dependencies. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/software-security/kev-exposure-checkExample request
curl -i -X POST "https://www.brainiac.software/api/v1/software-security/kev-exposure-check" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"components": [
{
"purl": "pkg:maven/org.apache.logging.log4j/log4j-core@2.14.1"
}
]
}
JSONAn unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.
FAQ
- Do I need an API key? No. Pay the listed USDC amount with x402.
- What network? Base (eip155:8453), USDC.
- Is this an official determination? No. Results are for human review against the cited sources.
Related operations
- Match SBOM vulnerabilities — $0.08 USDC
- Report dependency risk — $0.08 USDC
- Check licence compatibility — $0.05 USDC
- Check malicious dependencies — $0.06 USDC