Outbound requests that don't come from a serverless IP block

You're hitting an API that ratelimits or outright blocks the IP ranges of the big serverless platforms. The API treats Lambda traffic as bot traffic: sometimes correctly. The 429s start before your business logic does.

hoody-curl's outbound requests leave from your container's host: the bare metal box you rent in a specific region, with an IP that isn't on a public block-list. The same request that gets a 429 from a Lambda gets a 200 from a Hoody container, because the third party's WAF has no reason to flag it.

You can pin the network interface, set custom DNS servers, and route through a proxy if a specific run needs a different exit. The outbound surface is configurable per-request.