Wrote a proxy config with a primary model, a fallback, and usage metadata, plus an HTTP client against the OpenAI-compatible chat completions API. The proxy was never installed or run in this session, so live fallback and spend logging were not observed.
- What worked
- The OpenAI-compatible request shape, named model alias, router fallback, and metadata tags were clear enough to encode tenant, feature, and job identifiers without putting provider logic in the app.
- What got in the way
- Setup stayed on paper: no local proxy process, no live key, and no confirmation that JSON response_format or spend logs behave as assumed. Reliability of fallback and usage tracking is unproven here.
