Two connections, in either order
The provider side is about the AI. You create an API key in your provider’s console, set a spend limit there, and paste the key into SiteTrellis, which encrypts it. The key belongs to your account, so every agent you build can use it, and you can keep several keys from different providers.
The platform side is about your website. The widget is one script tag in a Shadow DOM, so it works on any site where you can add a script. Some builders hide that setting behind a paid plan or a code-injection area, which is where the platform guides help.
Neither side needs a developer if your platform has a custom-code box. If you have never used an API key before, the quickstart walks through both sides in about five minutes, and the BYOK AI chatbot page explains why the AI bill goes to you instead of through us.
Providers at a glance
All five providers work in the same way inside SiteTrellis. What differs is the account you need, the billing model and the small print. Prices change often, so the provider pages quote estimates from our model catalog and tell you which rows are not yet confirmed.
| Provider | Account you need | Worth knowing |
|---|---|---|
| Anthropic (Claude) | Anthropic Console with prepaid credit | Careful instruction following; credit must be topped up |
| OpenAI | OpenAI API platform account | API billing is separate from a ChatGPT subscription |
| Google Gemini | Google AI Studio key | A free tier exists but has low limits |
| DeepSeek | DeepSeek platform account with a balance | Review the data-location terms before using it |
| OpenRouter | OpenRouter account with credits | One key reaches models from several labs |
You do not have to choose once. Each agent has an ordered fallback chain, so you can start on one provider and put a second one behind it. Why one provider is a single point of failure explains the reasoning, and how to choose an LLM for website chat covers cost, speed and quality.
Platforms at a glance
| Platform | Where the snippet goes | Full guide |
|---|---|---|
| WordPress | A header and footer scripts plugin, or your theme | Install on WordPress |
| Shopify | The theme file theme.liquid | Install on Shopify |
| Wix | Custom Code in the site settings | Install on Wix |
| Squarespace | Code Injection | Install on Squarespace |
| Any website | Before the closing body tag, or a tag manager | Install on any website |
Using Google Tag Manager? The tag manager guide covers the trigger and consent settings. Single-page apps load the script once in the root HTML, as described in the widget JavaScript API docs.
What is not on this list
There are no native connectors for CRMs, helpdesks or calendars. To send leads or events elsewhere you use signed webhooks or an automation service, and to look something up in your own systems you use a custom HTTP tool. We would rather say so plainly than list logos we do not have. The features overview has the complete picture.