Skip to main content
You can create Maitai API keys in the Portal under Settings → API Keys.
api_keys

​
Maitai API key (required)

Set MAITAI_API_KEY: 
export MAITAI_API_KEY="<YOUR_MAITAI_API_KEY>"
Or pass it directly when constructing the client: 
import maitai

client = maitai.Maitai(
    maitai_api_key="<YOUR_MAITAI_API_KEY>",
)

​
Provider keys (optional)

Maitai can run requests across multiple providers. You can supply provider keys in two ways.

​
Option A: Environment variables

export OPENAI_API_KEY="<YOUR_OPENAI_API_KEY>"
export GROQ_API_KEY="<YOUR_GROQ_API_KEY>"
export ANTHROPIC_API_KEY="<YOUR_ANTHROPIC_API_KEY>"
export CEREBRAS_API_KEY="<YOUR_CEREBRAS_API_KEY>"
export SAMBANOVA_API_KEY="<YOUR_SAMBANOVA_API_KEY>"
export GEMINI_API_KEY="<YOUR_GEMINI_API_KEY>"
The Python SDK also supports DeepSeek (DEEPSEEK_API_KEY / deepseek_api_key).

​
Option B: Pass provider keys into the SDK constructor

import maitai

client = maitai.Maitai(
    maitai_api_key="<YOUR_MAITAI_API_KEY>",
    openai_api_key="<YOUR_OPENAI_API_KEY>",
    groq_api_key="<YOUR_GROQ_API_KEY>",
    anthropic_api_key="<YOUR_ANTHROPIC_API_KEY>",
    cerebras_api_key="<YOUR_CEREBRAS_API_KEY>",
    sambanova_api_key="<YOUR_SAMBANOVA_API_KEY>",
    gemini_api_key="<YOUR_GEMINI_API_KEY>",
    deepseek_api_key="<YOUR_DEEPSEEK_API_KEY>",
)
If your company has provider keys configured in the Portal, the SDK can automatically use them after it initializes (so you don’t have to set provider env vars in every environment).

​
Managing provider keys in the Portal

To better organize credentials across environments, you can store provider keys in the Portal and associate them with a Maitai key. This lets you keep MAITAI_API_KEY as the only required secret for most integrations. api_keys For best practice, create a separate Maitai key per environment, then attach the provider keys you want that environment to use. api_keys_edit