# Embed threat intelligence your users can check.

> WhisperGraph's query API puts threat intelligence and internet infrastructure answers inside your own product. Your users paste an address and see who runs it and what sits beside it, with the path that produced the answer.

*Source: https://www.whisper.security/solutions/security-vendors*
*Last updated: 2026-11-08*

---

- [Free Sign Up](https://console.whisper.security/sign-up)
- [Book a demo](https://meetings-eu1.hubspot.com/rsaggar)

## Building threat intelligence data in-house is a project of its own.

Every address your users paste comes with an expected story: who owns it, what else they run, whether it is listed anywhere, and how current that answer is. Joining naming, routing, ownership, certificate, physical and threat data across the internet, and keeping it current, takes its own team, separate from the product you are trying to ship.

## Threat intelligence for the product you build.

- **[Threat intelligence platforms](https://www.whisper.security/products/intelligence/use-cases/threat-investigation/indicator)**: Pivot from one indicator to the infrastructure behind it, inside the workflow your users already run.
- **[SIEM platforms](https://www.whisper.security/solutions/soc#in-your-siem)**: Enrich an alert when it fires with the owner, the network, its RPKI status and the feeds behind the indicator.
- **[EDR and endpoint security](https://www.whisper.security/products/intelligence)**: Show who runs the remote address a process reached, which network announces it, what else sits on that address and which feeds list it.
- **[Email security](https://www.whisper.security/products/intelligence/use-cases/dns-email-security/indicator-enrichment)**: Look past the headers: who hosts the sending domain, who registered it, what shares its address and which feeds list it.
- **[Brand protection](https://www.whisper.security/products/intelligence/use-cases/brand-protection/build-takedown-evidence-package)**: Take a look-alike your users found and show who hosts it, who registered it, what else sits on its address and which feeds list it.
- **[Exposure management](https://www.whisper.security/products/intelligence/use-cases/infrastructure-supply-chain/infrastructure-mapping)**: Show a domain's names, hosting, routes and RPKI status in one pass.

## Known clean is not the same as no data.

Every verdict carries a coverage value beside its score: known clean, malicious-evidenced, ambiguous, no data or listing stopped. Gate automation on coverage. The score alone cannot tell known clean from no data, and ambiguous belongs with a person.

Three hosts. A yes or no feed calls the first two clean and the third bad. Whisper calls them known clean, no data, and listed with sources. The feed’s clean for the brand-new host is the mistake.

- [Read the coverage contract](https://www.whisper.security/docs/whisper-graph/procedures/coverage)

## One graph behind every verdict your users see.

Every figure comes from the graph itself, stamped with the date it answered. Whisper runs its own network, AS219419, which you can check in the RIPE database.

[Run a query, no key](https://www.whisper.security/docs/whisper-graph/getting-started)

- **7B** Nodes (hostnames, addresses, networks, owners, facilities and feed listings)
- **40B** Edges (the relationships that join every layer to the next)
- **185** intelligence feeds (161 threat feeds, 24 VPN, proxy, Tor, ad-tracking, reputation and popularity lists)
- **21.6M** Threat listings (feed listings joined to the names and addresses they point at)

*Measured 2026-11-15*

## Your first threat intelligence API call.

One Cypher question over HTTPS. Your key goes in the header and the indicator goes in parameters, kept out of the query string. The values shown are reserved examples.

**curl**

```bash
curl -s -A "your-product/1.0" \
  -X POST https://graph.whisper.security/api/query \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $WHISPER_API_KEY" \
  -d '{"query": "MATCH (ip:IPV4 {name: $ip})-[:ANNOUNCED_BY]->(p:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN) RETURN ip.name AS ip, p.name AS route, p.rpkiStatus AS rpki, a.name AS asn, ip.verdictCoverage AS coverage LIMIT 1", "parameters": {"ip": "203.0.113.24"}}'
```

**Response**

```json
{
  "columns": ["ip", "route", "rpki", "asn", "coverage"],
  "rows": [{"ip": "203.0.113.24", "route": "203.0.113.0/24", "rpki": "valid", "asn": "AS64511", "coverage": "no-data"}]
}
```

- [Full API reference](https://www.whisper.security/docs/cypher-api/reference/query-post)
- [How embedding WhisperGraph works](https://www.whisper.security/products/engine/embed)

## Live now, behind one endpoint.

- **Query API**: Read-only Cypher over one endpoint. (Live)
- **MCP server**: Read-only, for any MCP client. (Live)
- **API reference**: Headers, parameter binding, the response envelope and every error, with code in five languages. (Live)
- **SIEM and TIP connectors**: Splunk, Sentinel, OpenCTI (STIX 2.1), MISP and Wazuh. (Live)
- **[On-prem and OEM](https://www.whisper.security/contact-us)**: Talk to us about OEM and on-prem deployment.

## Embed threat intelligence in four steps.

1. **Try the question your users ask**: Run it with a free key, against the same endpoint your product will call.
2. **Book a call**: Bring the questions your product needs answered.
3. **Get a key scoped to your product**: Separate from a normal account.
4. **Ship**: Your product calls the endpoint you tested against, and status.whisper.security reports its health.

## What security vendors ask first.

- **[Where does the data come from?](https://www.whisper.security/docs/whisper-graph/threat-feeds)**: WhisperGraph joins DNS records, the public BGP routing tables, WHOIS and RDAP registration data, certificate transparency logs, intelligence feeds, and records of data centres, exchanges, subsea cables and their landing points. Every answer your product receives carries the path through that data that produced it.
- **How current is the data?**: WhisperGraph sorts its data into four classes: live data that reaches the graph through the day; data refreshed on a regular cycle; data taken from periodic snapshots; and slow-changing reference records, like physical infrastructure and threat actors. DNS resolutions, routing, route-origin records and threat listings are live.
- **[What does "no data" mean?](https://www.whisper.security/docs/whisper-graph/procedures/coverage)**: "No data" means WhisperGraph holds no observation of that indicator, so there is nothing to judge it on. It is one of five coverage values a verdict carries: known clean, malicious-evidenced, ambiguous, no data and listing stopped. Gate automation on that value, and route ambiguous to a person.
- **How do terms work?**: Commercial terms for embedding WhisperGraph threat intelligence in a security product, including OEM use, are agreed per contract after a call about the questions your product needs answered. Before that call, your engineers can test the query API with a free key against the same endpoint your product will use.
- **[Can it run on-prem?](https://www.whisper.security/pricing)**: Running WhisperGraph on your own premises, or as an OEM deployment, is discussed per contract. Book a call and bring your hosting and data-residency requirements. Until then, your product calls the hosted query API at graph.whisper.security.

## Bring the question your users ask most.

Try it against the same endpoint your product will call, or talk it through with us first.

- [Free Sign Up](https://console.whisper.security/sign-up)
- [Book a demo](https://meetings-eu1.hubspot.com/rsaggar)
