Providers and keys

​

Overview

The Providers page in the AI Center is where platform admins connect AI providers. Each connection is a key. Chat, agents and AI pieces across your platform run on these keys. Connecting keys centrally means:

• Teams use company-managed provider accounts, not personal ones.
• Credentials are stored once, encrypted, and never shown to builders.
• You decide which models and which projects each key may use.

Go to Platform admin → AI Center → Providers. Keys are grouped by provider. Each row shows the key’s name, its status, how many models and projects it covers, and how many tiers use it. Providers you have not connected yet are listed under Also available.

​

Supported providers

​

Add a key

You can add more than one key for the same provider. For example, one Anthropic key for production work and another, with its own budget, for the marketing team.

​

Key status

Every key shows a status badge: The status updates on its own when AI calls succeed or fail. To check right now, open the key and click Recheck.

​

Key page

Click a key to open it. The page has three tabs.

​

Models

Choose which of the key’s models the platform may use:

• All models: every model the provider offers. New models from the provider are added automatically.
• Only selected: only the models you tick.

Search, sort (newest, cheapest, biggest context, name) and filter by tool calling, reasoning, vision or image generation. Each row shows the model’s context size and price per million tokens, when known. A model a tier uses shows Used by and the tier name, and stays selected until you change the tier. For Google Vertex AI, Cloudflare AI Gateway and Other (OpenAI Compatible), you type the model ids yourself, because these providers don’t list them.

​

Access

Choose which projects may use the key:

• All: every project on the platform.
• Only selected: only the projects you tick.
• All except: every project except the ones you tick. New projects get access automatically.

If a narrower list means a tier can no longer run in some projects, Activepieces asks you to confirm before saving.

​

Settings

• Name: rename the key.
• Credentials: click Replace to enter new credentials. Models and project access stay as they are.
• Delete this key: flows and agents that use this key will fail. A key that a tier still uses can’t be deleted; remove it from the tier first.

Changes to the models, projects and name are not saved right away. A bar at the bottom lets you Save or Discard them. Save or discard before you replace the credentials.

​

Default chat model

The Default chat model card at the top of the page sets the model every new chat starts on. Pick a tier or a model from one of your keys. If the chosen model can’t run in a project, for example because its key doesn’t serve that project, new chats there fall back to the default tier or another available model. The card shows a warning icon when this happens. If the model was removed, the card shows Use default to clear the choice.

​

AI credits

On Cloud, your plan includes AI credits through a built-in Activepieces provider. You don’t add a key for it, and it is not listed with your keys. Credits show up as their own options in the model pickers, and their usage is billed on your plan. You can mix credits and your own keys.

​

Plan

Your own AI keys need a plan that includes AI providers. Without it, the page shows a preview and an upgrade prompt. If your plan changes and no longer includes AI providers, existing keys become Read-only. You can’t open or edit them, but you can still delete them. Click Upgrade to get them back.

​

Cost control and logging

Spend on your own key is billed by your provider. To add limits and an audit trail, put a gateway in front of it:

• Set rate limits and budgets.
• Log and monitor every AI request.
• Track usage across projects.

OpenRouter and Cloudflare AI Gateway are set up like any other provider. Any other gateway that speaks the OpenAI API works through Other (OpenAI Compatible), so LiteLLM, Portkey, Helicone and self-hosted routers are all fine. Azure and AWS Bedrock give you the same through your cloud account’s quotas and logs.

​

Related

• Tiers: group models from your keys into named choices for builders.
• Capabilities: add web search, web scraping, image generation and embeddings.
• API reference: list keys, create a key, update a key, recheck a key, delete a key.