Enterprise workspaces can bring their own AI provider keys to Taskade. AI agents and automation steps then run on your OpenAI, Anthropic, or Google account, and your provider bills you directly.
TL;DR: On Enterprise, add your own OpenAI, Anthropic, or Google Vertex AI key to a space under Connections → AI Model Keys. AI agents and automation steps in that space then run on your provider account when they use a model from that provider. Anything left on Auto still uses Taskade credits. See the Plan Matrix and SSO setup.
In this guide, you will:
- Decide whether your own keys fit your team
- Add a provider key to a space
- See which AI requests run on your key
- Rotate a key without downtime
Inside the video: New: Bring Your Own AI Keys (BYOK) in Taskade Genesis AI Agents
Bring your own AI keys so that Taskade AI agents call the provider on your own account, with your billing and your rate limits. The video plugs in OpenAI and Anthropic keys and calls the result "compliance friendly, billing visible." Among the plans on sale, your own keys are an Enterprise feature.
Video: New: Bring Your Own AI Keys (BYOK) in Taskade Genesis AI Agents · 0:20 · published 2026-06-01 · Watch on YouTube
Key steps
- Get an API key from your AI provider.
- Add the key to the agent, as the video shows, or add it for a whole space under Connections → AI Model Keys.
- Pin a model from that provider on the agent. Requests from that agent then go to your provider account.
A key for a whole space is the default for every agent in that space. An agent left on Auto still uses Taskade credits, because Taskade picks the model for Auto.
Timestamps
- 0:02 Bring your own API keys
- 0:06 Your AI teammates call providers directly
- 0:08 Your account, your billing, your rate limits
- 0:11 Set keys in agent settings
- 0:13 Compliance friendly, billing visible
Try it: Plan Matrix · Create an agent · Create an AI Agent walkthrough
Before You Start
Your own keys need an Enterprise plan and a key from your AI provider.
| Requirement | Details |
|---|---|
| Plan | Enterprise. The AppSumo and PitchGround lifetime tiers also include it. |
| Who can do this | Members who can edit agents in the space. Other members do not see the panel. |
| What you need | An API key from OpenAI or Anthropic, or a service account key (JSON) from Google Cloud |
| Time | About 5 minutes for each provider |
Know When Your Own Keys Fit
Your own keys fit when your company must own the AI bill or the data path.
| Situation | Why your own key helps |
|---|---|
| Procurement approved your provider account | The AI bill lands on the provider invoice that finance already approves. |
| Compliance owns the data path | Traffic flows through the provider account where your audit log lives. |
| Your volume is high | You can negotiate better provider pricing than the bundled credits give you. |
For everything else, Taskade credits are simpler and need no key rotation.
Step 1: Add Your Keys
Keys live on the Connections page of a space, under AI Model Keys.
- Open the space that you want the keys to cover.
- Go to Connections and find AI Model Keys.
- Click Add key. The Add LLM API key dialog opens.
- Under Provider, pick OpenAI, Anthropic, or Google Vertex AI.
- Type a Key name, for example "Engineering key".
- Paste your API key. For Google Vertex AI, paste the Service account key (JSON) instead.
- Click Save key. Taskade checks the key with the provider before it saves it.
┌──────────────────────────────────────────────────────────────┐
│ AI Model Keys [ Add key ] │
│ Provider keys that agents and automations in this space │
│ run on. Keys are stored encrypted and never shown again. │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Connect Google Vertex AI FREE │ │
│ └────────────────────────────────────────────────────────┘ │
│ ┌────────────────────────────────────────────────────────┐ │
│ │ Engineering key ••••a1b2 Active │ │
│ │ OpenAI key added on [date] │ │
│ └────────────────────────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────────┘
The list shows each key by name, with only its last four characters or, for Google, the service account email. Repeat the steps for each provider that you want to use.
Where a Key Applies
A key belongs to the space where you added it, and it serves that space by default.
- One space, one set of keys. A subspace can use a different provider account than its parent.
- No setup for each agent. Inside the space, the key is the default for AI agents and for the built-in Taskade AI automation steps.
- A specific model is required. Your key serves only an agent or step whose model comes from that provider. Anything left on Auto uses Taskade credits, because Taskade picks the model for Auto.
- Google keys serve Google models only. The model menus do not list a Google model. A Google key serves only the agents and steps that already name one.
See What Runs on Your Keys
After you add a key, AI requests from these places go through your provider account.
| Surface | Runs on your key |
|---|---|
| Custom AI agents in agent chat, for a signed-in teammate | Yes, on a model that they pin from a provider that you added |
| Built-in Taskade AI steps, such as Ask AI and Categorize with AI | Yes, when the step's model comes from a provider that you added. A step on TSK-Auto uses Taskade credits. |
| Ask Agent steps and public agent embeds | Only when the key is set on that agent directly |
| Taskade Genesis app building and Taskade EVE chat | No |
| Models from providers that you did not add | No. They use Taskade credits. |
| Anything left on Auto | No. Taskade picks the model, so Taskade pays for it. |
Built-in Taskade AI steps offer TSK-Auto and the TSK tiers. Each TSK tier runs on a model from one provider. Run one test step on each tier that you use, then look in your provider dashboard to see which tiers your key serves. See Taskade AI for the menu on each step.
A key that you set on one agent yourself keeps working everywhere that agent runs. Tell your team about these rules before you turn on your own keys.
Step 2: Test Before You Cut Over
A test call in your provider dashboard proves that the key works.
- Pin a model from your provider on one agent, and send the agent a chat message.
- Set one Ask AI automation step to a TSK tier, and run it.
- Make sure that each call shows in your provider dashboard.
A test on Auto proves nothing, because Auto always runs on Taskade credits.
You Are Done When
Your key shows as Active under AI Model Keys, and your test calls show in your provider dashboard.
Rotate a Key
Taskade uses the newest active key for each provider, so a new key takes over from the old one.
- Make a new key in your provider dashboard.
- In the space, open Connections → AI Model Keys.
- Click Add key, pick the same provider, and paste the new key.
- Click Save key.
If no other tool uses the old key, revoke it at the provider.
Tips
- Limit who can rotate keys. Only members who can edit agents in a space see the AI Model Keys panel. Keep those roles tight and audited.
- Combine with SSO. Most teams that need their own keys also need single sign-on for governance.
- Keep automations on your key. Give each automation AI step a TSK tier that your key serves, not TSK-Auto.
Frequently Asked Questions
Which plans can bring their own AI keys?
Enterprise. The AppSumo and PitchGround lifetime tiers also include it. On other plans, the AI Model Keys panel does not show.
Which AI providers can I connect?
OpenAI, Anthropic, and Google Vertex AI. OpenAI and Anthropic take an API key. Google Vertex AI takes a Google Cloud service account key in JSON.
Does my key cover Taskade Genesis app building?
No. Taskade Genesis app building and Taskade EVE chat use Taskade credits. Your key covers AI agents and built-in AI automation steps that use a model from your provider.
Why does a request still use Taskade credits?
The agent or step is on Auto or TSK-Auto, or its model comes from a provider that you did not add. Pick a model from your provider to move the request to your key.
Can someone read my key after I save it?
No. Taskade stores keys encrypted and never shows them again. The list shows only the last four characters, or the service account email for Google.
Next Steps
Pair your keys with the rest of your Enterprise controls.
- Compare Enterprise: See what Enterprise unlocks in the Plan Matrix.
- Set up single sign-on: Follow SAML SSO with Google.
- Control who edits agents: See Roles and Permissions.
- Add per-step connectors: See Bring Your Own AI Key. Compare costs in AI Models & Credit Costs.
- Talk to sales: See Enterprise plan details on the Pricing page.