A production path for multi-provider inference

Production inference rarely fails because one HTTP request was difficult. It fails when routing, admission, provider health, and billing disagree about what should happen.

One decision record#

MEGA now records the provider candidates considered for each request, the policy that admitted the workload, and the route that ultimately served it. Operators can inspect the same decision without reconstructing it from unrelated logs.

Health before preference#

Preferred providers remain preferences, not promises. The router removes unhealthy or incompatible targets before applying price and latency priorities, so a configured preference cannot silently override runtime safety.

A narrow client contract#

Clients submit one MEGA request shape. Provider-specific credentials and protocol differences stay behind the routing boundary, which keeps application code stable as capacity changes.