The model is no longer the architecture
Model catalogs now change faster than most application release cycles. A model that wins on reasoning may lose on latency; a smaller model can be dramatically better for extraction; and a regional endpoint may be mandatory for sensitive data.
When those choices live inside product code, every provider change becomes an application migration. A gateway separates the stable contract your product depends on from the dynamic set of models behind it.
Route against outcomes, not brands
Humiris treats routing as a constrained decision. Teams define the bounds—budget, latency, privacy, capability and availability—then the router selects from the destinations that satisfy them.
The important part is traceability. Every decision should answer why a destination was eligible, which fallback was prepared and what the request ultimately cost.
Keep the application portable
A stable OpenAI-compatible surface keeps integration work small while routing policy evolves independently. You can begin with one managed key, connect your own provider accounts later and keep the same application code throughout.