Providers
The provider IDs Atoi recognizes, and how direct and routed access differ.
These are the provider IDs Atoi recognizes. You need one when a receipt, a qualified model name, or a command has to say which door a request went through.
| Provider id | What it is |
|---|---|
openai | Direct OpenAI access |
anthropic | Direct Anthropic access |
google | Direct Google access |
deepseek | Direct DeepSeek access |
kimi | Kimi access |
xai | xAI access |
openrouter | The OpenRouter catalog and routing |
gateway | Atoi's gateway routing |
Having an ID in this list does not mean every account has that provider enabled, or that every provider connects the same way. Setup lives in Models and keys.
#Per account status
A provider is saved, active, unavailable, or failed for your account. Enabled models are stored per provider. Saving a key can also refresh the model list.
#Direct and routed
The same upstream model can arrive through a direct provider, OpenRouter, or the gateway. Keep the provider-qualified ID when provenance, price, or error handling matters.
#Model names change
This page lists stable provider IDs only. Open Settings → Models for the live model list, then run a real request before you count on a lane.
Read Models and keys to connect one, or Model capabilities before you rely on a model.
Was this useful?