Bring Your Own AI Keys (Enterprise)

Overview

Enterprise workspaces can bring their own AI provider keys to Taskade. OpenAI and Anthropic traffic from Taskade Genesis app building, automations, and AI agents 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 and Anthropic API keys to their workspace. Once added, AI traffic for Taskade Genesis, agents, and automations runs against your account at your provider, not Taskade's shared credit pool. 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

The Owner of an Enterprise workspace adds the keys in workspace settings. Other roles cannot see or rotate them, by design.

1. Sign in as the workspace Owner.
2. Open Settings → AI Keys.
3. Pick the provider, OpenAI or Anthropic.
4. Paste your API key.
5. Save. Taskade verifies the key with the provider and confirms it is live.

Repeat for the second provider if you want both available. Keys are stored encrypted at rest and only used to send Taskade requests through your account.

What runs on your keys

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

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. Set this expectation with your team before turning AI key routing on.

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 Settings → AI Keys 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. Only the Owner sees the AI Keys panel. Keep Owner assignment tight and audited.
• Test before you cut over. Add the key, then run one Taskade Genesis prompt and one agent call to confirm both surfaces work before you remove the credit pool fallback for your team.
• 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. Owner is the only role that can add or rotate keys.
• Pricing. Enterprise plan details and how to talk to sales.