# OSV Vulnerability Record Lookup by ID

> OSV Vulnerability Record Lookup by ID is a paid API for AI agents from data.japanagent.dev, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Fetch a single vulnerability record by CVE, GHSA, or OSV ID from the OSV database, including summary, severity, affected packages, and fixed versions.

## Facts

- Endpoint: GET https://data.japanagent.dev/vuln/:id
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/osv-vulnerability-record-lookup-by-id-d062d648
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mHNrCdyDtBbrG1aMBMW_l

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 osv-vulnerability-record-lookup-by-id-d062d648
```

Example prompt: Can you pull up the full OSV record for CVE-2021-44228 — I need the severity rating, which packages are affected, and what versions have a fix?

## When to prefer this

Use this endpoint when you already have a specific vulnerability identifier (CVE, GHSA, or OSV ID) and need structured details about that single vulnerability. Prefer this over package-level vulnerability search when the exact advisory ID is known and you want authoritative severity, affected package, and patch version data from the OSV database.

## Known failure modes

- Invalid or malformed vulnerability ID returns 404 or error response
- ID exists in format but not found in OSV database returns empty or not-found result
- Network or upstream OSV API timeout returns 5xx error
- Malformed path parameter causes request routing failure

## How this service works

Fetch a single vulnerability record by ID (CVE, GHSA, or OSV ID) from the OSV database: summary, details, severity, affected packages and fixed versions.

## Output

Returns a structured vulnerability record from the OSV database including the vulnerability summary, description/details, severity score (CVSS or similar), a list of affected packages with ecosystem info, and the fixed versions available for remediation.

## 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"
    },
    "pathParams": {
     "type": "object",
     "required": [
      "id"
     ],
     "properties": {
      "id": {
       "type": "string",
       "description": "CVE-*, GHSA-*, or OSV-* vulnerability ID"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/osv-vulnerability-record-lookup-by-id-d062d648/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data.japanagent.dev](https://www.zero.xyz/host/data.japanagent.dev/llms.txt)