VulDB

{
  "service_type": "platform",
  "base_url": "https://vuldb.com",
  "auth_method": "api_key",
  "auth_config": {
    "api_key": { "in": "header", "name": "X-VulDB-API-Key", "description": "API key provided on registration" }
  },
  "endpoints": [],
  "pricing_model": { "type": "subscription", "details": { "plan": "commercial", "tiers": ["free trial", "paid plans"] } },
  "rate_limits": {},
  "capabilities": ["vulnerability database", "CVE research", "threat intelligence", "vulnerability search", "API access", "transactional bots"],
  "raw_analysis": "VulDB is a comprehensive vulnerability intelligence platform maintained by a community of researchers. It aggregates and enriches data from various sources like CVE, exploits, and threat feeds. The API is designed for security professionals, analysts, and developers to programmatically query vulnerability information, including details, metrics, and related exploits. It is a mature commercial service with free and paid tiers. The API is RESTful and requires key-based authentication, allowing automated scanning and integration into security workflows. Integrations are primarily via API, though the documentation also mentions transactional bots for automated updates. The service focuses on providing real-time, actionable threat data, with a strong emphasis on accurate and up-to-date records."
}

1/3 tests passed

```json
{
  "overall": 68,
  "dimensions": {
    "token_efficiency": 8.5,
    "first_try_success": 6.0,
    "response_parseability": 7.5,
    "error_clarity": 6.5,
    "doc_quality": 6.0,
    "auth_simplicity": 6.5,
    "latency": 7.0,
    "consistency": 7.0
  },
  "pricing_normalized": {
    "model": "subscription",
    "free_tier": "trial only",
    "entry_cost": "medium"
  },
  "issues": [
    "Website returns 403 on main page — potential bot protection or region blocking that may interfere with automated access",
    "no llms.txt file found — AI agents must rely on general documentation or scraping, reducing discoverability",
    "No clear getting-started flow visible from checks — onboarding may require manual exploration",
    "robots.txt restricts many subdirectories with crawl-delay 1s, which could slow automated data gathering"
  ],
  "recommendations": [
    "Add llms.txt to expose structured API and pricing info to AI agents — significantly reduces token overhead for discovery",
    "Consider relaxing 403 responses for common user agents or documenting bot access policy clearly",
    "Provide an API quickstart guide with curl examples to reduce first-try friction",
    "Explicitly document API response schemas and error codes for better parseability"
  ]
}
```