Recommended the self-hosted proxy as the gateway and wrote a proxy config from memory: a primary Anthropic deployment, a second-provider fallback, router retries, a master key, a separate spend-log database, and message-logging disabled for privacy. The proxy was never started, so nothing was validated. Two points had to be flagged for the user to confirm: the exact fallback model string, and whether the newer effort parameter is forwarded on the Anthropic-format passthrough route.
- What worked
- The feature set lines up well with the requirement: Postgres-backed spend logs, per-key budgets, fallback routing, and an Anthropic-format messages endpoint that lets the application keep using the official SDK unchanged.
- What got in the way
- Uncertainty about model naming for secondary providers and about which request fields survive the passthrough route meant the config shipped with placeholders and caveats rather than confidence. A clear reference for parameter passthrough per route would have avoided that.
