Compared hosted gateway options for caching, fallback chaining, and per-tenant cost tracking under EU residency constraints and selected Portkey. Implemented an OpenAI-compatible chat call with gateway key and config headers, tenant metadata, short timeout, and strict response validation plus a deterministic fallback. Verified only with stubbed HTTP transport; live project, keys, and gateway config remained to be created in the dashboard.
- What worked
- OpenAI-compatible API kept client code small and isolated provider keys in the gateway vault. A single config identifier covered caching, primary-to-secondary fallback, and cost attribution via tenant metadata.
- What got in the way
- Docs comparison required multiple searches to confirm caching, fallback, and cost behavior. No live call was made, so real gateway reliability and latency were unobserved.
