Route abliterated language models across providers with automatic fallbacks, modality-aware selection, and one place to compare availability and token prices.
Modality-aware selection is the part I would test first, since a router that picks well for text can still miss on other inputs. With availability and token prices compared in one place, the practical question is whether a fallback changes the cost mid-request, or if the price quoted up front is the one you actually pay.
Replies
The fallback is something I'd want to see in the response metadata. A successful request can still mean a different provider or model handled it.
@oleksii_sekundant great feedback thanks!
Modality-aware selection is the part I would test first, since a router that picks well for text can still miss on other inputs. With availability and token prices compared in one place, the practical question is whether a fallback changes the cost mid-request, or if the price quoted up front is the one you actually pay.