> ## Documentation Index
> Fetch the complete documentation index at: https://docs.decepticon.red/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration

> Configure API keys, model profiles, and environment settings for Decepticon.

## API Key Setup

Decepticon requires an LLM API key to power its agents. Run the interactive setup wizard:

```bash theme={null}
decepticon onboard          # Primary setup flow
decepticon onboard --reset  # Reconfigure from scratch
```

### Supported Providers

Decepticon uses **LiteLLM** as its model proxy, supporting any compatible backend:

| Provider            | Models                               | Notes                                |
| ------------------- | ------------------------------------ | ------------------------------------ |
| **Anthropic API**   | Claude Opus, Sonnet, Haiku           | Recommended for best performance     |
| **Anthropic OAuth** | Same models, via Claude subscription | Use Claude Code OAuth credentials    |
| **OpenAI**          | GPT-5.5, GPT-5.4, GPT-5-nano         | Full support with automatic fallback |
| **Google**          | Gemini 2.5 Pro / Flash / Flash-Lite  | Via LiteLLM proxy                    |
| **MiniMax**         | MiniMax-M2.5, MiniMax-M2.5-lightning | Alternative high/mid tier            |
| **Custom**          | Any LiteLLM backend                  | Self-hosted or alternative providers |

### Environment Variables

You can also configure via environment variables:

```bash theme={null}
# Primary provider
export ANTHROPIC_API_KEY="sk-ant-..."

# Or OpenAI
export OPENAI_API_KEY="sk-..."

# Or set via LiteLLM config for custom backends
```

## Model Profiles

Decepticon routes different agent roles to different model tiers for optimal cost/performance balance:

| Profile  | Orchestrator | Exploit    | Recon      | Use Case                                           |
| -------- | ------------ | ---------- | ---------- | -------------------------------------------------- |
| **eco**  | Opus 4.7     | Sonnet 4.6 | Haiku 4.5  | Production — best cost/performance ratio (default) |
| **max**  | Opus 4.7     | Opus 4.7   | Sonnet 4.6 | High-value targets — maximum capability            |
| **test** | Haiku 4.5    | Haiku 4.5  | Haiku 4.5  | Development/CI — fast iteration                    |

Each profile includes automatic fallback chains. If the primary provider is unavailable or rate-limited, Decepticon seamlessly switches to the next provider in the chain (e.g., Opus 4.7 → GPT-5.5 → Gemini 2.5 Pro → MiniMax-M2.5).

<Info>
  Select your profile during `decepticon onboard` or set it at any time via the `DECEPTICON_MODEL_PROFILE` environment variable. The `eco` profile is the default and recommended for most operations.
</Info>

## C2 Configuration

Sliver C2 integration is profile-based via Docker Compose. The `COMPOSE_PROFILES` environment variable is read from your `.env` (or shell) before the launcher starts the stack — it is not a flag to the `decepticon` command itself. Sliver is enabled by default.

```bash theme={null}
# .env (default)
COMPOSE_PROFILES=c2-sliver

# Or override per-run via shell
COMPOSE_PROFILES=c2-sliver decepticon
```

When enabled, the Sliver team server starts on the operational network with:

* Auto-generated operator configuration
* Pre-installed `sliver-client` in the sandbox
* mTLS, HTTPS, and DNS C2 channel support

<Card title="C2 Integration" icon="satellite-dish" href="/en/features/c2-integration">
  Learn more about Sliver C2 integration and C2 channel configuration.
</Card>

## Docker Resources

Decepticon runs entirely in Docker containers. Recommended resource allocation:

| Component          | CPU      | Memory | Notes                                      |
| ------------------ | -------- | ------ | ------------------------------------------ |
| LangGraph Platform | 1 core   | 1 GB   | Management network — agent orchestration   |
| LiteLLM Proxy      | 0.5 core | 512 MB | Management network                         |
| PostgreSQL         | 0.5 core | 512 MB | Management network — engagement state      |
| Neo4j              | 1 core   | 1 GB   | Bridges both networks — knowledge graph    |
| Web Dashboard      | 0.5 core | 512 MB | Management network — Next.js               |
| Kali Sandbox       | 2 cores  | 4 GB   | Operational network — runs offensive tools |
| Sliver C2          | 1 core   | 1 GB   | Operational network (default profile)      |

<Warning>
  The Kali sandbox requires the most resources as it runs the full offensive toolkit. Allocate at least 4 GB of memory for stable operation during complex engagements.
</Warning>