cookbook/90_models/xai/README.md
Note: Fork and clone this repository if needed
python3 -m venv ~/.venvs/aienv
source ~/.venvs/aienv/bin/activate
XAI_API_KEYexport XAI_API_KEY=***
uv pip install -U openai ddgs duckdb yfinance agno
python cookbook/92_models/xai/basic_stream.py
python cookbook/92_models/xai/basic.py
python cookbook/92_models/xai/tool_use.py
python cookbook/92_models/xai/image_agent.py
python cookbook/92_models/xai/image_agent_bytes.py
python cookbook/92_models/xai/image_agent_with_memory.py
Sign in with a SuperGrok subscription through the OAuth device flow instead of
setting XAI_API_KEY. The stored token is encrypted with a dedicated key:
export XAI_TOKEN_ENCRYPTION_KEY=***
Generate a key with python -c "from agno.utils.encryption import generate_encryption_key; print(generate_encryption_key())"
python cookbook/90_models/xai/oauth_device_login.py
Sign in from inside the conversation instead of the terminal: a sign-in agent hands the user an approval link on one turn and finishes the sign-in on the next, and a Grok agent then answers on the subscription. Two agents, because an agent cannot sign in to the model it is already running on - so the sign-in agent runs on a model that does not need the SuperGrok session. Use this for chatbots and web UIs.
export OPENAI_API_KEY=***
export XAI_TOKEN_ENCRYPTION_KEY=***
python cookbook/90_models/xai/oauth_chat_signin.py
Several people share one deployment and each spends their own subscription. The
token is stored under the user_id the run carries, and the model resolves that
user's token per request. A user who has not signed in falls back to the
deployment's own session; require_user_token=True on the model refuses that
fallback and requires everyone to sign in first. Per-user tokens need a
database - one token file cannot hold a session each. Same two keys as above:
python cookbook/90_models/xai/oauth_multi_user.py