Providers
Overview
A Provider is an LLM service registered against your organisation that supplies the model an agent will use at runtime. You register a provider once with its API key and from then on any agent in your organisation can pick a model from it.
Providers live under Automation → Custom Agents → Providers.
Supported provider types
| Provider | Provider type ID | Notes |
|---|---|---|
| OpenAI | openai | All chat-capable OpenAI models. |
| Anthropic | anthropic | Claude family. Streaming is enabled by default to support long max-tokens. |
| Gemini | gemini | Google Gemini chat models. |
| OpenRouter | openrouter | Aggregator — gives you access to a large catalogue of models from a single key. |
| DeepSeek | deepseek | DeepSeek chat and reasoner models. |
The platform also supports cloud-hosted variants of OpenAI (Azure), Anthropic (Bedrock, Vertex), and Gemini (Vertex). Contact your Zynap administrator if you need to register one of these — they require additional configuration outside the standard provider form.
Adding a provider
- Open Automation → Custom Agents → Providers.
- Click New provider in the top-right of the list.
- Fill in the form:
| Field | Required | Description |
|---|---|---|
| Provider name | Yes | A friendly label, e.g. Anthropic Claude or Engineering OpenAI. Used in agent dropdowns. |
| Provider | Yes | Choose one of the supported provider types. Cannot be changed after creation. |
| API key | Yes | The provider's secret. Stored encrypted; never shown again after save. |
- Click Save provider.
The provider then appears in the providers list and is available to all agents in the organisation.
Editing a provider
Click a provider's row to open its detail page, then make changes:
- Provider name can be changed at any time.
- Provider type is fixed once a provider is created. To switch to a different vendor, create a new provider and update your agents to point at it.
- API key must be re-entered to be saved. The form does not show the existing key — leaving the field blank means "no change".
Models
You don't register models manually. After a provider is saved, the platform automatically fetches the catalogue of models that key has access to and exposes them in the Agent form's model dropdown. The model list is keyed off the provider, so each provider in your org can expose a different catalogue.
When the catalogue can't be fetched live (provider API outage, rate-limiting, network blip), the agent form falls back to a cached list and shows a hint: "Models loaded from cache — provider API may be unavailable."
Deleting a provider
Click a provider's row to open its detail page, then click Delete.
A provider cannot be deleted while one or more agents reference it — the delete will return an error listing the agents you need to reassign or delete first.
API key handling
| What you provide | Where it goes |
|---|---|
| A new API key | Encrypted and stored against this provider. |
| An empty key on edit | The existing key is kept. |
| A new key on edit | The old key is replaced. |
API keys are never returned to the browser after they're saved. The edit form will always show an empty password field, regardless of whether one is stored.
Best practices
- One provider, many agents. Register a provider once per vendor and reuse it across agents. There's no benefit to creating multiple rows for the same vendor unless you want to scope them to different budgets or rate limits.
- Name them by purpose, not by vendor. A name like "R&D Anthropic (high quota)" tells your team more than "Anthropic".
- Rotate keys via the edit form. Generate a new key on the vendor's dashboard, paste it into the provider edit form, save — the old key stops being used immediately.
- Test with a cheap model first. When verifying a provider works, pair it with a cheap model in a throwaway agent before binding it to production workflows.
Troubleshooting
| Issue | Resolution |
|---|---|
| Models dropdown is empty in the agent form | The provider key is rejected by the vendor or the vendor API is down. Check the Models loaded from cache hint and verify the API key on the vendor's dashboard. |
| "Invalid API key" on save | The key was rejected by the platform's quick validation call. Verify it on the vendor dashboard and paste it again. |
| Cannot delete a provider | One or more agents still reference it. Edit those agents first or delete them. |
| Edit form does not show the current key | Expected. The key is write-only — leave blank to keep, paste a new value to replace. |
Updated: 2026-05-04