Empirical Security
Empirical Security builds data-driven models that predict which vulnerabilities will actually be exploited, so security teams can prioritize remediation by real-world risk instead of raw CVSS severity. It operates the Foundation (global) model, which combines real-time internet exploitation telemetry with EPSS and monitors 18,000+ exploited CVEs; hourly-updated EPSS models (epss_v3, epss_v4, epss_v5); and Radiant, an organization-specific model that layers your local assets, configurations and internal telemetry on top of the Foundation data. The read-only REST API exposes CVE detail, per-model scores and percentiles, malware hashes, critical indicators, score history, change history, full dataset export, search, and saved CVE groups, secured with OAuth 2.0 client credentials (JWT bearer). Empirical Security is backed by Costanoa Ventures.
Empirical Security publishes 3 API contracts indexed on the APIs.io network: CVE Groups API, Search API, and CV Es API. Tagged areas include Company, Security, Cybersecurity, Vulnerability Management, and Vulnerability Prioritization.
The Empirical Security catalog on APIs.io includes 1 Spectral governance ruleset.
Empirical Security’s developer surface includes documentation, API reference, getting-started guide, engineering blog, signup flow, authentication, and 19 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| ServiceNow Store (partner apps + ServiceNow Certified App) | standard | 19.4 (thin) | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 2
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
APIs 3
Individual APIs this provider publishes, each with its own machine-readable definition.
Empirical Security CVE Groups API
Saved CVE queries and their execution.
Empirical Security Search API
Query CVEs using Empirical search syntax.
Empirical Security CV Es API
Retrieve CVE detail, scores, malware hashes and history.
Open Collections 3
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Empirical Security CVE Groups API
OPEN COLLECTIONEmpirical Security CVE Groups CVEs API
OPEN COLLECTIONEmpirical Security CVE Groups Search API
OPEN COLLECTIONAgent Skills 2
Packaged agent skills for driving this provider's APIs from an AI assistant.
Monitor a saved CVE group
AGENT SKILLPrioritize CVEs by exploitation probability
AGENT SKILLSpectral Rules 1
Spectral governance rulesets for linting and validating these APIs.
Empirical Security API Rules
SPECTRALOpenAPI Overlays 1
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 3
Authentication, authorization, and security posture
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Empirical Security API — frequently asked questions
Does Empirical Security have an API?
Yes. APIs.io lists 3 APIs from Empirical Security, including Empirical Security CVE Groups API, Empirical Security Search API and Empirical Security CV Es API.
Is there an OpenAPI specification for the Empirical Security API?
Yes. APIs.io indexes 3 OpenAPI specifications for Empirical Security, each linked for download from this page.
How do I authenticate with the Empirical Security API?
Empirical Security documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Empirical Security Authentication.
Is the Empirical Security API ready for AI agents?
Empirical Security has a Kin Score of 33.7 out of 100 (thin) and an Agent Readiness score of 34.2 (agent-ready), scored by API Evangelist on 2026-11-02.
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.