OEM

One endpoint. Your product answersinfrastructure questions.

Put Whisper's graph inside your own product. One Cypher endpoint answers your users' infrastructure questions across BGP, DNS, WHOIS, certificates and hosting, priced and metered per call.

Priced and metered per call. No rate card on this page.

Talk to the foundersRead the Cypher API docs
What you get

The whole graph, behind one call.

The schema

Every arrow is a question your product can ask.

The entity types and the named edges between them, grouped by layer. One call crosses as many of them as the question needs.

  • DNS · Web
  • Mail · SPF
  • WHOIS
  • Routing · RPKI
  • GeoIP
  • Threat intel
  • Physical
DNS · WebMail · SPFWHOISThreat intelGeoIPRouting · RPKIPhysical infrastructureCHILD_OFNAMESERVER_FORCHILD_OFMAIL_FORSPF_INCLUDEREGISTERED_BYHAS_REGISTRARHAS_EMAILRESOLVES_TOLISTED_INBELONGS_TOANNOUNCED_BYLOCATED_INLISTED_INHAS_COUNTRYROUTESHAS_NAMEBGP_NEIGHBORAUTHORIZES_ORIGINAUTHORIZES_PREFIXAS_PRESENT_ATIX_MEMBERIX_HOSTED_ATLANDING_NEARCABLE_LANDS_ATBELONGS_TONAMESERVERSUBDOMAINTLDHOSTNAMEMAIL_SERVERSPF_SENDERORGANIZATIONREGISTRAREMAILFEED_SOURCECATEGORYCITYCOUNTRYIPV4 · IPV6PREFIXANNOUNCED_PREFIXROAASNASN_NAMEASN (peer)INTERNET_EXCHANGEFACILITYCABLE_LANDINGSUBMARINE_CABLE
The highlighted trail is one query: hostname, address, prefix, network, building.
Read the schema
Metering

Priced and metered per call.

A call

One Cypher query answered, whether it returns one row or a thousand.

What is metered

Every call against your key, whatever endpoint or catalog recipe issued it.

The invoice

Measured usage. Seats do not come into it.

The rate

Negotiated per contract. There is no published rate card for embedding.

Bring your expected call volume, and the founders quote against it.

Talk to the founders
The first call

The request your product sends.

One POST, one JSON envelope of columns and rows back.

cURL
curl -s -A "whisper-client/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 (h:HOSTNAME {name: \"google.com\"})-[:RESOLVES_TO]->(ip:IPV4) RETURN ip.name AS ip LIMIT 5"}'
Support

The support model.

Support runs through the same channel every Whisper customer uses: email and the console ticket portal, with a response time set in your contract.

Scope

What the graph does not hold.

Whisper answers infrastructure questions: who owns something, how it is routed, and what else is nearby. File reputation and identity breaches are out of scope.

  • No file hashes

    The graph has no malware or file-reputation data.

  • No URLs

    It resolves hostnames and addresses. Paths are out of scope.

  • No compromised-identity data

    It holds no breach, credential or personal-data feeds.

Get started

How to start.

  1. Talk to the founders

    Bring your expected call volume and the questions your product needs answered.

    Talk to the founders

  2. Get a metered key

    Your key is scoped and billed for embedding, apart from a normal account.

  3. Send your first call

    The same Cypher endpoint every Whisper customer uses. Your product sends the request.

    Read the Cypher API docs

Put the graph inside your product.

Talk to the founders with your expected call volume.

Talk to the foundersRead the Cypher API docs