WhisperGraph, embedded
Your product answers infrastructure questions.
One endpoint behind it.
Put WhisperGraph inside your own product. One Cypher endpoint answers your users' questions across routing, DNS, ownership, certificates, hosting and threat intelligence.
The whole graph, behind one call.
One endpoint
Read-only Cypher over the whole graph, with one JSON envelope back.
Batch verbs
Score or enrich a whole list in one round trip, each row with its coverage label.
The workflow catalogue
Prepared investigations to run as they are or adapt.
Evidence per answer
Every verdict carries its sources, so your users see why.
Your first 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 -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"}}'{
"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"}]
}Three steps.
Talk to the founders
Bring the questions your product needs answered.
Get a key scoped to your product
Scoped for embedding, apart from a normal account.
Ship
Your product calls the endpoint you tested against, and status.whisper.security reports its health.
Put the graph inside your product.
Talk to the founders with the questions your product needs to answer.