Gateway routing

The gateway centralizes model targets, fallback and operation budgets:

from zhivex_ai import GatewayConfig, GatewayModelTarget, create_gateway

Configure an explicit target list and cost policy. A strict cost ceiling requires known pricing; unknown prices must not silently bypass the budget. Application-owned ModelCatalog, ModelCatalogEntry, create_model_catalog, and capability/pricing metadata are Stable. The maintained default_model_catalog snapshot remains Beta and affects routing only when explicitly configured. A provider’s API host is separate from the author of its hosted model.

Terminal attempt observations describe actual completion or failure. Keep observers bounded and redact request data before export. Review the gateway guide and reference before configuring retries or fallback in a production service.