Motiontator: One API and one balance across model providers

I'm building Motiontator for developers who already use more than one model API provider. When one provider fails, switching the endpoint is only part of the work. You also have another balance, another usage history and another set of routing decisions to manage. Motiontator moves that provider management behind one API endpoint and one balance. New requests filter eligible routes by model, endpoint, key policy and health before comparing estimated cost. Supplier review includes manual checks for suspected model substitution, undisclosed downgrades and unusual output. These checks have limits; there is no promise of perfect model identification. The retry limits matter: streaming, tool, stateful and image requests aren't automatically replayed at another provider. An alternate attempt is bounded and available only for eligible stateless, non-streaming text without tools. This isn't a promise that a request can never fail. I'd value feedback from developers who already juggle multiple providers: what would you need to see before trusting a single gateway with that work? Routing and compatibility notes: https://motiontator.online/en/do...