Gateway profiles
Connect Anthropic-compatible HTTPS gateways and map their provider model IDs without changing isolated profile behavior.
Connect a gateway
Create a Gateway profile when a provider exposes an Anthropic-compatible HTTPS endpoint. OreoDeck stores the endpoint with that profile and stores the gateway API key only in macOS Keychain; it never writes the key to the project, profile config, or this website.
A gateway profile is separate from a Claude subscription profile. It reports its own local token/cost telemetry, not Claude subscription billing.
Map provider models
Model mapping is optional. After a successful connection check, map the provider’s returned model ID to Opus, Sonnet, Haiku, or Fable. Leave any field blank to preserve Claude Code’s default model ID for that family.
| Claude family | Gateway mapping |
|---|---|
| Opus | Optional provider model ID |
| Sonnet | Optional provider model ID |
| Haiku | Optional provider model ID |
| Fable | Optional provider model ID |
Check before use
Use Check connection to make an explicit read-only request to the gateway’s models endpoint. OreoDeck displays model choices only when the gateway returns them; a connection that does not advertise models can still be saved with manual mappings.
If discovery fails, first confirm the HTTPS URL, the gateway key in Keychain, and the provider’s Anthropic compatibility. Do not paste a gateway key into a terminal command or a project file to troubleshoot it.