[APP] Whisper (verifiable agent IPv6 identity - keyless verify + keyed control plane and graph)

**Name of app / service**

Whisper - verifiable IPv6 identity for AI agents (AS219419, `2a04:2a01::/32`), plus the whisper.security internet graph. Each agent gets a real, routable IPv6 `/128` that *is* its identity: it can be looked up and confirmed by anyone, anywhere, with stock `dig`, `curl`, `whois`, and `openssl`.

**Link to developer documentation**

- Platform overview: https://whisper.online/platform
- Registry / RDAP / WHOIS: https://nic.whisper.online
- Public keyless API base: https://rdap.whisper.online
- Security graph and Cypher API: https://www.whisper.security/docs/cypher-api

**Auth schema requested**

`custom_auth` with a single **optional** secret field:

- `api_key` (secret, optional) - the account's `whisper_live_` API key, sent as `X-API-Key`.

The app is deliberately two-tier: the identity verification actions read a fully public, keyless API and keep working with the field left blank; the control-plane and graph actions require the key and raise a clear configuration error when it is missing. If an optional auth field is not supported, a required `api_key` works too and only narrows the keyless tier to connected users.

**Is lack of support preventing you from moving forward, or do you have a workaround?**

Contributing a new app: PR #21299. Review of that PR is currently waiting on the `whisper` app existing in the Pipedream registry.

**Are there specific actions or triggers you'd like to see for this app?**

Implemented in PR #21299 (43 actions):

- Keyless identity: Verify Agent Identity, Lookup RDAP Record, Get Transparency Log, Get Inbound Lookups, Get Egress IP
- Control plane (API key): Register Agent, List Agents, Get Agent, Allocate Identity, Connect Egress, Set Policy, Get Logs, Revoke Agent
- Graph intelligence (API key): Graph: Run Cypher, plus 29 named recipes (threat investigation, typosquat scanning, attack-surface mapping, BGP and routing audit, and more)