Use the Retell AI CLI from KosmoKrator to call Retell AI tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.
Retell AI can be configured headlessly with `kosmokrator integrations:configure retell-ai`.
# Install KosmoKrator first if it is not available on PATH.curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash# Configure and verify this integration.kosmokrator integrations:configure retell-ai --set api_key="$RETELL_AI_API_KEY" --enable --read allow --write ask --jsonkosmokrator integrations:doctor retell-ai --jsonkosmokrator integrations:status --json
Credentials
Authentication type: API keyapi_key. Configure credentials once, then use the same stored profile from
scripts, coding CLIs, Lua code mode, and the MCP gateway.
Key
Env var
Type
Required
Label
api_key
RETELL_AI_API_KEY
Secret secret
yes
API Key
url
RETELL_AI_URL
URL url
no
API Base URL
Call Retell AI Headlessly
Use the generic call form when another coding CLI or script needs a stable universal interface.
Every function below can be called headlessly. The generic form is stable across all integrations;
the provider shortcut is shorter but specific to Retell AI.
retell-ai.retell_ai_create_call
Write write
Create a new AI-powered phone call using a Retell AI voice agent. Specify the agent ID and optional metadata to attach context to the call.
Create a new voice AI agent in Retell AI. Specify the voice ID and system prompt. Additional options like agent name, language, and behavior settings can be provided.
Retrieve current Retell AI account information, including available agents and account status. Useful for verifying connectivity and understanding account capabilities.
Create a new voice AI agent in Retell AI. Specify the voice ID and system prompt. Additional options like agent name, language, and behavior settings can be provided.
Retrieve current Retell AI account information, including available agents and account status. Useful for verifying connectivity and understanding account capabilities.
Headless calls still follow the integration read/write permission policy. Configure read/write defaults
with integrations:configure. Add --force only for trusted automation that should bypass that policy.