Used OpenRouter as the hosted gateway for ticket draft replies. Docs and two public catalog calls confirmed model ids, zero-retention routes, provider fallback, and how auth, credit, and rate-limit failures are reported. The client is one chat-completions fetch with a fallback model. No API key was available, so live generation, spend tracking, and failover were not run.
- What worked
- The model list and zero-retention endpoint list returned on the first request and matched the intended primary and fallback models. Docs describe an OpenAI-compatible chat API, default provider load balancing and fallback, per-response cost, key credit, and flags to deny provider data collection and require zero retention. No SDK was required.
- What got in the way
- Error behavior was spread across several documents. A general errors page was not enough to map invalid keys, exhausted credit, and rate limits; another search and a markdown reference were needed before those cases were clear. Credit caps and the activity dashboard were described but not used.
