Bring Your Own AI Keys (Enterprise)

Overview

Enterprise workspaces can bring their own AI provider keys to Taskade. OpenAI, Anthropic, and Google traffic from your AI agents and your automations then routes through the keys you supply, billed by your provider on your account. Useful for legal, compliance, and cost-control reasons that often come up in a procurement review.

TL;DR: Enterprise plans can add their own OpenAI, Anthropic, and Google keys to a space, under Connections → AI Model Keys. AI agents and the built-in Taskade AI automation steps in that space then run against your account at your provider, not Taskade's shared credit pool, whenever they name a specific model. Pricing on your side, governance on your side. Pair with SSO setup and the enterprise plan matrix. Talk to sales to enable.

When this is the right choice

Bring-your-own-key is a fit when one of these is true.

• Procurement signed off on your provider account, not Taskade's. Your finance team needs the AI bill on the provider invoice they already approve.
• Compliance owns the data path. Your security review needs traffic to flow through the provider account where their audit log lives.
• Volume is high enough to justify direct billing. You can negotiate better provider pricing than the bundled credit model gives you.

For everything else, Taskade's bundled credit pool is simpler, cheaper to start, and avoids key rotation work.

How to add your keys

Keys live on the Connections page of a space, under AI Model Keys. Anyone who can edit agents in that space can add or replace one. Everyone else never sees the panel.

1. Open the space you want the keys to cover.
2. Go to Connections and find AI Model Keys.
3. Click Add key and pick the provider: OpenAI, Anthropic, or Google (listed as Google Vertex).
4. Paste your API key. For Google, paste the Google Cloud service account file instead.
5. Save. Taskade verifies the credential with the provider and confirms it is live.

Repeat for each provider you want available. Keys are stored encrypted at rest, shown only as a last-four or an account email afterwards, and used only to send Taskade requests through your account.

Google is the cheapest way in. Creating a Google Cloud service account costs nothing, and every call it serves uses zero Taskade AI credits.

Where a key applies

A key belongs to the space you added it to, so a subspace can run on a different provider account than its parent. Inside that space it becomes the default for both AI agents and the built-in Taskade AI automation steps, with no per-agent setup.

One condition decides whether a key is used: the agent or step has to name a specific model. Anything left on Auto keeps running on Taskade credits, because Auto picks the model on Taskade's side. Picking a model from a provider you have not connected also falls back to the credit pool.

What runs on your keys

After the keys are in place, AI traffic from these surfaces routes through your provider account.

The five built-in Taskade AI steps do not all offer the same models. Ask AI and Generate with AI show the full model menu, so they can reach any of the three providers you connect. Respond with AI, Prompt AI, and Categorize with AI keep a short curated list of OpenAI models, so an OpenAI key is the only one they can use. See Taskade AI for the per-step picker.

If a model the user picks comes from an open-source provider or a vendor you have not added a key for, that step falls back to Taskade's bundled credit pool. The same happens on Auto. Set this expectation with your team before turning AI key routing on.

The gaps are deliberate. A space key is workspace-wide configuration, and calls it serves cost no Taskade credits, so anonymous visitors on a public agent embed and machine-triggered automation replies stay on the credit pool. That keeps your workspace balance as the throttle on surfaces nobody is watching. A key you set on one agent yourself is an explicit choice and keeps serving everywhere it always did.

Rotating a key

You rotate keys the same way you rotate any provider key. Generate a new one at the provider, paste it into Taskade, save. The old key stops accepting traffic the moment the new one validates.

• Generate the new key in the provider dashboard.
• Open Connections → AI Model Keys in the space and paste the new value.
• Save. Taskade switches over within seconds.
• Revoke the old key at the provider when you're sure no other tool depends on it.

Tips

• Limit who can rotate keys. The AI Model Keys panel is visible only to members who can edit agents in that space. Keep those roles tight and audited.
• Test before you cut over. Add the key, then pin a model from that provider on one agent and send it a chat message, and pin the same model on one Ask AI automation step and run it. Confirm both land in your provider dashboard before you rely on this for your team. Testing on Auto proves nothing, because Auto always routes through Taskade.
• Combine with SSO. Most teams that need their own keys also need single sign-on for governance. The two pair naturally on Enterprise.

Related guides

• Plan Matrix. What Enterprise unlocks compared to lower tiers.
• SAML SSO with Google. Pair with single sign-on for full enterprise governance.
• AI Models & Credit Costs. The credit pool you replace, plus the open-source providers that still route through Taskade.
• Roles and Permissions. Which roles can edit agents, and therefore add or rotate keys.
• Bring Your Own AI Key. The separate per-step provider connectors for automations.
• Pricing. Enterprise plan details and how to talk to sales.