Here's a simpler fix. A sister program to pscp is psftp, which is interactive. The first time you run it from a command window, it gives you the fingerprint and asks if you want to cache it. I logged in with the SQL Server Agent account, ran psftp, and now my job runs with no problem.