Setting up your API keys

Some extension features need a key from another service. You set those once in Settings and they are used whenever an extension you build needs them.

Go to Settings from your account menu, under AI and Web Search Keys. Keys are stored securely and injected into the extensions you generate.

Groq

For AI features running on Groq inference. Get a key from the Groq Console.

Gemini

For features using Google's Gemini models. Get a key from Google AI Studio.

Parallel Web Search

For extensions that need to search the web. Get a key from Parallel AI.

Each has a toggle, so you can keep a key saved but switched off.

Supabase

If your extension needs user accounts or a database, turn on Supabase Authentication and add two things from your Supabase project: the project URL and the anon key. Both are in your Supabase dashboard under Project Settings, then API.

One thing worth doing on the Supabase side: enable Row Level Security and create your tables before expecting the extension to save anything. Without that the extension can connect but will not be able to write.

Whose keys these are

Yours. You pay each provider directly at their prices, and we add nothing on top. Setting a key here is not a subscription with us.

If you work in a team

Keys can also be set at workspace level, so everyone in a workspace shares them. See the workspaces article.