Hey Product Hunt — I built UltimateRouter because “just call the model” somehow became a journey through a harness router, agent router, model router, provider router, inference router, tool router, and API router. UltimateRouter turns that mess into one inspectable graph. It shows where a request went, why each hop selected the next one, what every hop added in latency and cost, and whether the direct path would have been better. The launch build includes a working Routing Studio with four policies, an installable ur CLI with stdin and JSON, a versioned contract for 16 router classes, native protocol drivers, explicit NOT_CONFIGURED states, and a Routing Receipt for every completed path. The satire is intentional, but the calls and traces are real when you connect an endpoint. I’d love to know: which router in your stack creates the most invisible latency, and when should UltimateRouter tell you to remove one instead of adding another? Thanks for taking the roundabout.

UltimateRouter

See, call, and audit every router in your stack

See, call, and audit every router in your stack