I fell into the trap myself. Future::HTTP uses whatever other event loop you already have loaded. If you have no event loop loaded, it uses HTTP::Tiny, which is synchronous.

The "correct" approach is to load the event loop first (use IO::Async; (or whatever)) and then load/use HTTP::Future.

I should make this more clear in the documentation resp. fix the usage so that this trap does not exist anymore.