suggestion

[charis3306]

ZoomEye requires a key call instead of an account login.

[sophymarine]

Right now, resources/scripts/api/zoomeye.ads logs in with raw username and password credentials to grab a temporary JWT. Those bearer tokens expire after 24 hours. That timeout causes silent authentication failures during long-running cron scans and automated mapping loops. Switching the script to accept persistent API keys using the API-KEY header fixes the session issue completely. It also keeps cleartext passwords out of shared configuration files. Has anyone already started mapping the api_key parameter into the ADS config template?