canonical: https://jentic.com/apis/vuldb.com/vuldb

# VulDB API

VulDB is a vulnerability database providing comprehensive information about software vulnerabilities, exploits, countermeasures, and cyber threat intelligence (CTI). The API uses a single POST endpoint with various parameters to query vulnerability data, perform searches, and retrieve CTI information. All requests consume credits based on the query type and detail level. The API exposes 1 endpoints secured with apiKey authentication.

## For AI agents

Programmatically query the vuldb database. Covers 1 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for security only.

## Capabilities

- Query the VulDB database
- Manage security data programmatically
- Integrate VulDB API into automated workflows
- Query and filter VulDB API records by parameters
- Monitor VulDB API operational status and events

## Use cases

### Security Operations

Use the VulDB API to perform security operations programmatically. The API provides 1 endpoints covering core functionality including query the vuldb database.

Example prompt: Call POST / to query the vuldb database

### Data Retrieval and Monitoring

Query VulDB API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary VulDB API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call VulDB API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'query the vuldb database', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/` | Query the VulDB database |

## Key resources

- **Vulnerabilities** — Query and search vulnerability entries
- **CTI** — Cyber Threat Intelligence queries
- **Lookups** — Vendor and product lookups

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 93 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/vuldb.com/vuldb/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the VulDB API by hand means sending your personal key in the X-VulDB-ApiKey header (or as an apikey POST field), posting to the single vuldb.com endpoint, and shaping every query yourself. Through Jentic you install once, import the VulDB API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** The VulDB API exposes a single POST query endpoint rather than per-resource URL paths, so limit the agent to that read query operation it needs. The rule stays operations-only, so the agent can look up vulnerability records and nothing beyond the operations you allow.
- **Credential handling:** Your VulDB API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'query recent vulnerabilities', and Jentic returns the matching VulDB API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Snyk** — Alternative security API
- **Crowdstrike** — Alternative security API

## FAQ

### What authentication does the VulDB API use?

The VulDB API uses an API key passed in the `X-VulDB-ApiKey` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I query the vuldb database with the VulDB API?

Yes. Use the POST / endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the VulDB API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I query the vuldb database through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'query the vuldb database'. Jentic returns the matching VulDB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the VulDB API have?

The VulDB API exposes 1 endpoints covering vulnerabilities, cti, lookups operations.

### Can I limit what my agent is allowed to do with the VulDB API?

Yes. The VulDB API exposes a single POST query endpoint rather than per-resource paths, and because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Scope the agent to just that read query operation, so it can look up vulnerability and CTI records and do nothing beyond the operations you allow. Your API key is stored encrypted by your own instance and injected only when an allowed call runs.