Security advisories: Use when a user asks whether a CVE is actively exploited, which vu…

What it does

Security advisories: Use when a user asks whether a CVE is actively exploited, which vulnerabilities in a vendor or product to patch first, whether it is used in ransomware campaigns, or needs CISA KEV due dates, required actions and FIRST EPSS exploit probability in one call.

Tags: security-advisories · open-data · verified-sources · bazaar

Call contract

Method

GET

Input

query parameters

Output

json

Last paid call

2026-10-12

{
  "limit": "5",
  "ransomware": "known",
  "vendor": "Microsoft"
}

{
  "dataset": "security-advisories",
  "limit": 5,
  "offset": 0,
  "records": [
    {
      "cve_id": "CVE-2015-5477",
      "cwes": [
        "CWE-19"
      ],
      "epss": 0.99409,
      "kev": true,
      "kev_date_added": "2026-10-08",
      "kev_due_date": "2026-10-11",
      "known_ransomware_use": "Unknown",
      "paid_placement": false,
      "product": "BIND",
      "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.",
      "retrieved_at": "2026-10-12T05:43:52.551073+00:00",
      "source_id": "cisa-kev",
      "source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
      "summary": "ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.",
      "vendor": "ISC",
      "verification": "open-data",
      "vulnerability_name": " ISC BIND Data Processing Errors Vulnerability"
    }
  ],
  "total": 1,
  "updated": "2026-10-12T00:00:00Z"
}

Use with an agent

1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
2. Inspect. Fetch /resources/35121.json for the price and payment options.
3. Pay. Call GET https://agentdatafeed.com/v1/security-advisories. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price

$0.003 / request

Protocol

x402 v2

Auth

No account or API key. Pay per request.

Networks

Base

Demand

1 calls · 1 unique payers in 30d (public x402 Bazaar data)

x402 payment requirements

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0x3EDa32e2315084dd09C8913694840Fe6006557Ee",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "3000",
    "amountUsd": 0.003,
    "maxTimeoutSeconds": 120
  }
]

Schemas

{
  "properties": {
    "example": {
      "type": "object"
    },
    "type": {
      "type": "string"
    }
  },
  "required": [
    "type"
  ],
  "type": "object"
}

{
  "example": {},
  "type": "string"
}

Examples

curl "https://agentdatafeed.com/v1/security-advisories"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

const res = await fetch("https://agentdatafeed.com/v1/security-advisories");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

import httpx
res = httpx.get("https://agentdatafeed.com/v1/security-advisories")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider

agentdatafeed.com

Endpoint

https://agentdatafeed.com/v1/security-advisories

Machine-readable

/resources/35121.json