Install and Configure
Comprehensive setup guide for the AIP SDK with advanced configuration options, security best practices, and troubleshooting tips.
Requirements
Python 3.10 or higher (3.11+ recommended)
Operating System: Windows, macOS, or Linux
Network: Internet access for package installation
Install SDK and CLI Together
Installing glaip-sdk provides both the Python SDK and the aip CLI. Pick the install command that matches how you manage dependencies.
pip (Linux/macOS)
pip install --upgrade glaip-sdkUse when you manage environments with venv or system Python. Activate the environment before running the command.
pip (Windows PowerShell)
pip install --upgrade glaip-sdkRun inside an elevated PowerShell session if your organisation restricts installs. Use py -m pip install --upgrade glaip-sdk when pip is not on PATH.
Poetry (project managed)
Ideal when the SDK ships with your application code. poetry run ensures the CLI uses the project virtual environment.
uv tool
Great for users who prefer reproducible global installs while keeping Python projects isolated.
pipx (CLI only)
Deploys the CLI in an isolated environment and keeps your global Python clean. Ideal for operations or QA stations. Recommended for data developers who only need the CLI.
--upgrade(or the equivalent) ensures you pick up the latest release or refresh an existing installation.Using a virtual environment? Activate it first, then run the same command.
Verify the CLI once installed:
Configure Access Options
Choose the option that matches your workflow. Each method sets the same API URL and API key; you only need one of them.
.env file (project scoped)
Shell profile (persistent)
Use when you want the SDK and CLI available in every terminal.
Linux / macOS:
Add the lines to
~/.bashrc,~/.zshrc, or your shell profile to persist them.Windows PowerShell:
Restart the terminal after running
setxso the variables are picked up.
Interactive CLI (per machine)
Run the built-in helper to store credentials in the CLI config file:
You will be prompted for:
API URL
API Key
This is convenient on developer laptops or CI agents that already store the values securely.
Verify Installation
Confirm both the CLI and SDK can reach your AIP instance.
Expected output includes ✅ Connected to AIP Platform.
aip status may also report:
⚠️ Partial Connection
DNS/SSL failure or blocked outbound request after the client connects.
Check VPN/proxy settings, verify AIP_API_URL, and retry from a network with internet access.
❌ Connection failed
Credentials missing or rejected before any data flows.
Re-run aip configure or export AIP_API_KEY/AIP_API_URL, then rerun the command.
Timed out
CLI could not reach the API within the configured timeout.
Confirm the service is up and adjust --timeout if your environment requires longer waits.
If the error mentions Temporary failure in name resolution, your DNS cannot resolve the host—double-check the URL or try again once network connectivity is restored.
Security Best Practices
These apply to anyone handling API keys for the platform—whether you are a developer, DevOps engineer, or administrator.
Use different API keys per environment (development, staging, production).
Never commit keys to source control—prefer secret managers or CI variables.
Rotate keys regularly and revoke unused ones promptly.
Optional CLI Configuration Helpers
Use these after installation when you need to inspect or adjust saved values.
Continue
Ready to run your first agent? Head to the Quick Start and follow the Python or CLI track.
Last updated