> For the complete documentation index, see [llms.txt](https://sandgarden.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandgarden.gitbook.io/docs/administration/supported-providers.md).

# Supported AI Providers

On the Bring Your Own Key and Open Source Software plans, Doc Holiday runs all writing on an AI provider key your organization supplies. OpenAI is Doc Holiday's native provider, and several other providers are supported at different levels. On the Enterprise plan Doc Holiday manages inference for you and none of this page applies; see [Billing and plans](/docs/administration/billing-and-plans.md).

### Provider support levels

| Provider      | Support level   |
| ------------- | --------------- |
| OpenAI        | Fully supported |
| Anthropic     | Supported       |
| AWS Bedrock   | Supported       |
| OpenRouter    | Supported       |
| Google Vertex | Experimental    |
| Gemini        | Experimental    |
| Groq          | Experimental    |
| Cerebras      | Experimental    |

**Fully supported.** Doc Holiday is built and tested against OpenAI. Every feature works as documented, and new features land here first.

**Supported.** Doc Holiday runs the full workflow end to end on these providers. Output quality and run cost can differ from OpenAI.

**Experimental.** Doc Holiday accepts keys for these providers, but they are not regularly tested. Use them at your own risk: runs may fail, and output quality may fall short of the supported providers.

### Using more than one provider

Keys are managed on the [AI Provider Keys](/docs/administration/ai-provider-keys.md) page. If your organization stores keys for more than one provider, an OpenAI key always wins. Without an OpenAI key, Doc Holiday selects the provider by a fixed order: Anthropic, Gemini, Groq, Cerebras, OpenRouter, AWS Bedrock, Google Vertex. Active and failover keys within one provider behave as described in [AI Provider Keys](/docs/administration/ai-provider-keys.md).

### Provider notes

* **AWS Bedrock** and **Google Vertex** authenticate with structured credentials (AWS access credentials and a GCP service account) instead of a single API key; the add-key dialog collects the extra fields.
* Keys must support real inference. A key that can only list models fails verification.

### Next

* Add a key in [Add your AI provider key](/docs/getting-started/add-your-ai-provider-key.md).
* Manage rotation and failover in [AI Provider Keys](/docs/administration/ai-provider-keys.md).
* Compare plans in [Billing and plans](/docs/administration/billing-and-plans.md).