Read hosted docs to compare caching, provider fallback and spend attribution for dashboard summaries. Docs supported a single OpenAI compatible client across two providers with gateway side cache and fallback chain plus workspace metadata for cost tracking. Selected this gateway and implemented against it without a live account.
- What worked
- Concepts for cache keys, fallback config and per workspace attribution were clear enough to design a thin client with no new datastore.
- What got in the way
- Details were spread across multiple pages and needed several fetches to confirm fallback and cache behavior.
