Router by Ramp

The thread mostly treated the launch as another entry in the suddenly crowded model-routing race, with the Stripe/OpenRouter news looming over every reaction. Several readers saw the timing as too neat to ignore and folded Router into a broader complaint: every established software company now seems compelled to ship the same AI stack of chatbot, agent framework, and model switchboard. That skepticism was sharpened by the product’s promise to choose the ideal model. Commenters argued that such a claim needs unusually transparent coverage, evaluation, and tradeoff data, not broad marketing language. The most concrete objection was the gap between repeated claims of supporting every model and a catalog that one reader considered far short of mainstream coverage. A company representative invited specific missing-model requests and pointed to published support documentation, while also quickly repairing a broken link to the list. That response softened the operational complaint but did not settle whether the branding accurately describes the service. Healthcare-facing buyers raised a separate concern about the lack of business-associate agreements, suggesting a router is not useful for sensitive AI workloads unless contractual accountability follows the request across providers. Readers also noted that access is currently limited to the United States. Interest in model-selection research and eventual directory inclusion existed, but the dominant mood was wary rather than impressed.