How much does CVE Search cost?

CVE Search costs 4 sats per call.

What does CVE Search return?

The endpoint returns matched CVEs with severity, KEV signal, dates, and direct detail URLs from the NVD dataset.

Is it useful for agents and triage workflows?

Yes. It is useful for turning product names, exploit terms, or vulnerability keywords into a normalized vulnerability result set.

CVE Search API • Live on Bitcoin mainnet

Search CVEs by keyword or product.

Use a funded session to search the NVD dataset by keyword and return normalized vulnerability matches with severity, KEV signal, dates, and detail links. Built for triage, enrichment, and security-agent workflows.

4 sats / call

POST /api/cve-search

NVD-backed search

What It Does

CVE Search turns a keyword, product, or vulnerability phrase into a compact set of normalized CVE matches. It is useful when an agent or analyst has a lead like a software name or issue type but not a specific CVE ID yet.

Returns matched CVEs from the official NVD feed
Includes severity, KEV signal, and publish dates
Provides direct detail URLs for follow-up review
Useful for search-driven triage and enrichment flows

Why It Helps

Most automation starts with imperfect clues, not exact identifiers. CVE Search gives you a first-pass vulnerability result set that can be ranked, filtered, or handed off to deeper follow-up calls like CVE Lookup.

Good fit for product-name and issue-type searches
Lets agents pivot from text to concrete CVE IDs
Pairs naturally with `cve-lookup` for exact enrichment
Current deployment is Bitcoin mainnet

Example Request

curl -X POST https://arkapi.dev/api/cve-search \
  -H "Authorization: Bearer ak_your_token" \
  -H "Content-Type: application/json" \
  -d '{"query":"wordpress information disclosure","limit":10}' | jq

Use a funded token from the Fund page. The endpoint is also documented in /openapi.json for agents and wrappers.

Example Body

{
  "query": "wordpress information disclosure",
  "limit": 10
}

query is required
limit is optional
Use product names, issue classes, or exploit-related terms

Example Response

{
  "success": true,
  "data": {
    "results": [
      {
        "cve_id": "CVE-2024-12345",
        "severity": "HIGH",
        "has_kev": false,
        "published": "2026-02-14T00:00:00Z",
        "title": "Information disclosure issue in WordPress plugin",
        "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-12345"
      }
    ]
  },
  "cost_sats": 4,
  "response_ms": 214,
  "endpoint": "/api/cve-search"
}

Good Uses

Search for CVEs related to a product before patch review
Turn incident keywords into concrete vulnerability candidates
Feed agent workflows that need likely CVE matches first, then deeper lookup
Build alerting and enrichment around product-risk monitoring

For broader platform usage, see the main docs and the live catalog.