Provider table
| Provider | Default Model | Auth | Tool-Use | Env Var |
|---|---|---|---|---|
| Anthropic | claude-sonnet-4-6 | API key | Yes | ANTHROPIC_API_KEY |
| OpenAI | gpt-5.4 | API key | Yes | OPENAI_API_KEY |
gemini-3.1-pro | API key | No | GOOGLE_API_KEY | |
| DeepSeek | deepseek-v3 | API key | No | DEEPSEEK_API_KEY |
| Mistral | mistral-large-latest | API key | No | MISTRAL_API_KEY |
| Ollama | llama3.2 | None (local) | No | N/A |
| HuggingFace | meta-llama/Llama-4-Scout-17B-16E-Instruct | API token | No | HUGGINGFACE_API_KEY |
How provider resolution works
ai-blackteam resolves your API key in this order:- CLI flag - passed directly via
--api-key - Environment variable - e.g.
ANTHROPIC_API_KEY - Config file - stored in
~/.ai-blackteam/config.yaml
- CLI flag -
--model claude-opus-4-20250115 - Config file -
providers.anthropic.default_model - Provider default - hardcoded in the provider class
Setting a key via config
~/.ai-blackteam/config.yaml. You can also use environment variable references in the config file:
${VAR_NAME} syntax at load time.
Setting a key via environment
{PROVIDER}_API_KEY for all providers.
Using a different model
Override the default model for any run:Tool-use support
Only Anthropic and OpenAI currently support tool-use attacks (agent exploitation, MCP exploitation, multi-agent attacks). These attacks require the provider’ssend_with_tools method.
If you run a tool-use attack against a provider that doesn’t support it, ai-blackteam will skip it and tell you why.