# KEV Entry Status Lookup

> KEV Entry Status Lookup is a paid API for AI agents from oracles-production.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns stored detail for a single Known Exploited Vulnerability (KEV) entry by entityId

## Facts

- Endpoint: GET https://oracles-production.up.railway.app/v1/kev/status
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/kev-entry-status-lookup-85f39cfb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_WufCzDeWi3XaZhW0BR868

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 kev-entry-status-lookup-85f39cfb
```

Example prompt: Can you pull up the KEV entry details for CVE-2026-12345 from the known exploited vulnerabilities catalog?

## When to prefer this

Use this endpoint when you need to look up a specific CVE entry from the CISA Known Exploited Vulnerabilities catalog by its entityId. Prefer this over general CVE databases when you specifically need KEV classification status and stored oracle data, especially in automated security workflows or threat intelligence pipelines.

## Known failure modes

- Entity not found if the CVE ID does not exist in the KEV store
- Invalid entityId format returns an error
- Payment of $0.01 USDC required per call; payment failure blocks the request
- Missing or malformed query parameter may return empty or error response

## How this service works

Stored detail for a single KEV entry (entityId like 'cve:CVE-2026-12345').

## Output

Returns a KEV entity object containing stored details for the specified CVE entry, including vulnerability metadata and exploitation status information. If no entityId is provided, returns a list of all tracked KEV entities.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string",
       "description": "entityId to look up; omit to list tracked entities"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "properties": {
      "entity": {
       "type": "object"
      }
     }
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/kev-entry-status-lookup-85f39cfb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oracles-production.up.railway.app](https://www.zero.xyz/host/oracles-production.up.railway.app/llms.txt)