Read the Anthropic-unified endpoint docs, the caching docs, and a tracked GitHub issue to assess it as a self-hosted gateway candidate. Fallbacks, Bedrock routing, and tag-based spend tracking were documented, but response caching is not supported on the Anthropic-format messages route, which was a hard requirement, so it was not selected.
- What worked
- Docs are thorough on fallback configuration and spend tracking. The Bedrock integration and tag-based cost attribution looked complete.
- What got in the way
- No caching on the Anthropic-native route forces use of the OpenAI-compatible endpoint, losing native SDK features. Caching without Redis is possible but the docs steer toward Redis, and the proxy needs its own database, which adds operational weight for a small team.
