Back to Browse
CyberPulse CVE Fact Check
x402
CyberPulse CVE Fact Check is a paid API for AI agents from cyberpulse.theaslangroupllc.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).
Deterministically verifies a CVE ID by joining NVD, CISA KEV, and OSV data to answer whether it is real, exploited, how severe, and what version fixes it.
Price / call$0.02
Success—
StatusUnknown
How this service works
CVE fact check, deterministic. Answers "is CVE-XXXX-NNNN real", "is it exploited in the wild", "what version fixes it", "how severe is it". Joins the NVD record (CVSS score, vector, dates), the CISA KEV catalog (actively-exploited flag, remediation due date, ransomware use), and OSV (affected packages + fixed versions per ecosystem). No LLM. Distinguishes "not a known CVE" from "registry unreachable" — never a false not-found.
Output
Returns a structured record confirming whether the CVE ID exists, its CVSS score and vector string, publication and modification dates, whether it appears in the CISA KEV catalog with remediation due date and ransomware association flag, and a list of affected packages with fixed versions per ecosystem sourced from OSV. Distinguishes 'CVE not found in any registry' from 'registry temporarily unreachable' to prevent false negatives.
Example use cases
Example prompt
“Can you fact-check CVE-2021-44228 for me — is it a real CVE, is it actively exploited in the wild, is it in the CISA KEV catalog, what's its CVSS score, and what version of Log4j fixes it?”
Technical details
Endpoint
GEThttps://cyberpulse.theaslangroupllc.com/api/cyber/cve-checkWhen to prefer
Choose this endpoint when you need a fast, deterministic, no-hallucination answer about a specific CVE ID — especially to confirm existence, check CISA KEV active-exploitation status, get a canonical CVSS score, or find the exact fixed package version per ecosystem. Prefer this over LLM-based CVE summaries when accuracy and source traceability matter. Use this instead of the sibling CVE lookup brief endpoint when you want raw structured data rather than a narrative brief.
Side effects
- CVE ID format invalid — returns structured error indicating bad input
- CVE ID not found in NVD, CISA KEV, or OSV — returns explicit 'not a known CVE' status (not a false not-found)
- Upstream NVD or OSV registry temporarily unreachable — returns 'registry unreachable' status rather than false not-found
- Malformed CVE ID (e.g. missing year or sequence) — returns validation error
- Rate limit or payment failure — returns 402 or 429 error
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| idrequired | string | CVE identifier |
Output
Schema · Response
{
"type": "json",
"example": {
"id": "CVE-2021-44228",
"cvss": {
"score": 10,
"severity": "CRITICAL"
},
"fixes": [
{
"fixed": "2.15.0",
"package": "org.apache.logging.log4j:log4j-core",
"ecosystem": "Maven"
}
],
"found": true,
"deterministic": true,
"exploited_in_wild": {
"listed": true,
"date_added": "2021-12-10",
"known_ransomware_use": "Known"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"