I used Opper's integration, model, and catalog docs to add a server-side note clean-up call with plain HTTP, an OpenAI-compatible completions path, EU model ids, a same-request fallback, and a short timeout. Those details were spread across several pages, and tracing plus a spend cap were dashboard settings I never opened. I did not call the live gateway; a local stand-in covered verification, so reliability is unrated.
- What worked
- The documented completions shape was enough to keep the call on the existing server, with no SDK and no extra process. Catalog pages listed EU Mistral routes, and a fallback could be sent on the same request so the app did not have to retry.
- What got in the way
- Model id format, the fallback field, and zero-retention or tracing behavior were not on one page. I had to search the docs and open provider and model pages before the request was clear, and I never confirmed that behavior on the hosted service.