.env.example

# ============================================================================
# Teradata Agent Recipes - Environment Configuration Template
# ============================================================================
# Copy this file to .env and populate with your actual credentials.
# DO NOT commit the .env file to version control (it contains secrets).
# ============================================================================

# ----- Tier 1: Core Database Access (Required by all recipes) -----

# Teradata host - ClearScape Analytics or on-premises instance
# Example: myinstance-xxx.env.clearscape.teradata.com
TD_HOST=your-teradata-host-here

# Teradata username
TD_USER=your-username

# Teradata password
TD_PASSWORD=your-password

# LLM API Key - depends on your chosen provider
# For OpenAI: sk-... (get from https://platform.openai.com/api-keys)
# For Anthropic: claude-... (get from https://console.anthropic.com)
# For Bedrock: AWS credentials set via AWS CLI
LLM_API_KEY=your-api-key-here

# LLM provider to use (optional, defaults to openai)
# Options: openai, anthropic, bedrock, litellm
LLM_PROVIDER=openai

# LiteLLM API URL (optional, only needed if using litellm provider)
# This should be the full HTTP endpoint to your liteLLM proxy's chat completions API.
# LiteLLM is an open-source proxy that unifies access to multiple LLM providers.
#
# Examples:
#   - Local liteLLM server: http://localhost:4000/v1/chat/completions
#   - Remote liteLLM proxy: https://litellm-proxy.example.com/v1/chat/completions
#
# When using liteLLM:
#   1. Start your liteLLM proxy: litellm --model <provider_model>
#   2. Set LLM_PROVIDER=litellm in .env
#   3. Set LITELLM_URL to your proxy endpoint
#   4. Set LLM_API_KEY to your API key (forwarded to the actual provider by liteLLM)
#
# See https://docs.litellm.ai/docs/proxy/intro for setup instructions.
# LITELLM_URL=http://localhost:4000/v1/chat/completions


# ----- Tier 2: MCP Server Access (Required by enterprise-templates: governed) -----

# URL to your Teradata MCP (Model Context Protocol) server
# Example: https://mcp-server.example.com:8443
# TD_MCP_URL=your-mcp-server-url


# ----- Tier 3: Advanced Features (Required by enterprise-templates: vector-search, open-analytics) -----

# Teradata Unified Execution Server (UES) URI for vector search and Open Analytics Framework
# Example: https://ues.example.com or http://localhost:9443
# TD_UES_URI=your-ues-uri

# Personal Access Token for UES authentication
# TD_PAT=your-pat-token

# Path to PEM certificate file for TLS authentication
# This should be an absolute path to a .pem file on your system
# TD_PEM_PATH=/absolute/path/to/your/certificate.pem