API Funnel 

The frustration that started this was simple: every time I needed to stitch together two external APIs, combine the responses, rename some fields, apply a bit of logic. I ended up writing the same boilerplate proxy code from scratch. A Node route here, an Express middleware there. It worked, but it felt like infrastructure I shouldn't have to build every single time. API Funnel started as a personal tool to stop writing that code. The idea was a visual canvas where you wire up external API calls as input nodes, map and transform the fields you care about, and publish a single clean endpoint at a real URL, no server to manage, no boilerplate. What surprised me most during the build was how many different people hit the same wall: frontend devs who need a backend proxy without spinning up a server, teams exposing legacy SOAP services as REST, developers hiding API keys behind a clean public-facing endpoint. The use cases converged on the same core need, a transformation layer between external APIs and the thing consuming them. Still early, still rough in places. But the endpoints are real, the URLs are callable, and I'd love to know what you think.