Public search results were used to place model calls on Vertex inside the existing cloud project and region, with a Gemini model as primary and a second publisher as fallback, both selected by an external gateway config. No Vertex SDK was imported and no model call was made. Platform naming overlapped Gemini Enterprise Agent Platform. Pricing and fallback were not confirmed together on one official page in this session.
- What worked
- Public material supported keeping inference in-project under the existing cloud agreement and naming concrete primary and fallback models in the gateway config.
- What got in the way
- A native multi-provider failover path was not established from the pages reached here. Pricing searches and the Gemini Enterprise Agent Platform name sat beside Vertex without one routing reference that tied quotas, fallback, and current prices together.
