What changed
Roder adds Synthetic as a first-party inference provider. The integration includes built-in model aliases, an OpenAI-compatible chat-completions transport, model discovery, and setup guidance.
Synthetic appears in provider menus even before credentials are configured, which makes the option discoverable from inside the CLI.
Why it matters
- Users can discover Synthetic and understand the setup path without leaving Roder or guessing configuration keys.
- Concrete model IDs and friendly aliases both work, which keeps quick experiments short while preserving explicit model routing for reproducible runs.
- Missing keys fail locally with actionable guidance instead of turning into vague provider errors during a turn.
Setting it up
Configure SYNTHETIC_API_KEY or the [providers.synthetic] table, then select Synthetic from the same provider surfaces used by the rest of Roder.