Integrations
Ailiv Agent connects to external systems for AI inference, tool servers, IDE workflows, programmatic access, and more. These integrations extend what Ailiv can do and where it can run.
If you only have time to set up one integration, set up an AI provider — a single API key gets you a working model.
AI Providers & Routing
Ailiv supports multiple AI inference providers out of the box. Use ailiv model to configure interactively, or set them in config.yaml.
- AI Providers — OpenRouter, Anthropic, OpenAI, Google, and any OpenAI-compatible endpoint. Ailiv auto-detects capabilities like vision, streaming, and tool use per provider.
- Provider Routing — Fine-grained control over which underlying providers handle your OpenRouter requests. Optimize for cost, speed, or quality with sorting, whitelists, blacklists, and explicit priority ordering.
- Fallback Providers — Automatic failover to backup LLM providers when your primary model encounters errors. Includes primary model fallback and independent auxiliary task fallback for vision, compression, and web extraction.
Tool Servers (MCP)
- MCP Servers — Connect Ailiv to external tool servers via Model Context Protocol. Access tools from GitHub, databases, file systems, browser stacks, internal APIs, and more without writing native Ailiv tools. Supports both stdio and SSE transports, per-server tool filtering, and capability-aware resource/prompt registration.
Web Search Backends
The web_search and web_extract tools support eight backend providers, configured via config.yaml or ailiv tools:
| Backend | Env Var | Search | Extract | Crawl |
|---|---|---|---|---|
| Firecrawl (default) | FIRECRAWL_API_KEY | ✔ | ✔ | ✔ |
| SearXNG | SEARXNG_URL | ✔ | — | — |
| Brave (free tier) | BRAVE_SEARCH_API_KEY | ✔ | — | — |
| DuckDuckGo (ddgs) | (none) | ✔ | — | — |
| Exa | EXA_API_KEY | ✔ | ✔ | — |
| Parallel | PARALLEL_API_KEY | ✔ | ✔ | — |
| xAI | XAI_API_KEY | ✔ | — | — |
Quick setup example:
web:
backend: firecrawl # firecrawl | searxng | brave-free | ddgs | tavily | perplexity | keenable | exa | parallel | xai
If web.backend is not set, the backend is auto-detected from whichever API key is available. Self-hosted Firecrawl is also supported via FIRECRAWL_API_URL.
Browser Automation
Ailiv includes full browser automation with multiple backend options for navigating websites, filling forms, and extracting information:
- Browser Use Cloud — Managed Chromium with stealth, residential proxies, CAPTCHA solving, and reusable browser profiles
- Browserbase — Alternative cloud browser provider with managed browsers, anti-bot tooling, CAPTCHA solving, and residential proxies
- Local Chromium-family CDP — Connect to your running Chrome, Brave, Chromium, or Edge browser using
/browser connect - Local Chromium — Headless local browser via the
agent-browserCLI
See Browser Automation for setup and usage.
Voice & TTS Providers
Text-to-speech and speech-to-text across all messaging platforms:
| Provider | Quality | Cost | API Key |
|---|---|---|---|
| Edge TTS (default) | Good | Free | None needed |
| ElevenLabs | Excellent | Paid | ELEVENLABS_API_KEY |
| OpenAI TTS | Good | Paid | VOICE_TOOLS_OPENAI_KEY |
| MiniMax | Good | Paid | MINIMAX_API_KEY |
| xAI TTS | Good | Paid | XAI_API_KEY |
| NeuTTS | Good | Free | None needed |
Speech-to-text supports eight providers: local faster-whisper (free, runs on-device), a local command wrapper, Groq, OpenAI Whisper API, Mistral, xAI, ElevenLabs Scribe, and DeepInfra. Voice message transcription works across Telegram, Discord, WhatsApp, and other messaging platforms. See Voice & TTS and Voice Mode for details.
IDE & Editor Integration
- IDE Integration (ACP) — Use Ailiv Agent inside ACP-compatible editors such as VS Code, Zed, and JetBrains. Ailiv runs as an ACP server, rendering chat messages, tool activity, file diffs, and terminal commands inside your editor.
Programmatic Access
- API Server — Expose Ailiv as an OpenAI-compatible HTTP endpoint. Any frontend that speaks the OpenAI format — Open WebUI, LobeChat, LibreChat, NextChat, ChatBox — can connect and use Ailiv as a backend with its full toolset.
Memory & Personalization
- Built-in Memory — Persistent, curated memory via
MEMORY.mdandUSER.mdfiles. The agent maintains bounded stores of personal notes and user profile data that survive across sessions. - Memory Providers — Plug in external memory backends for deeper personalization. Eight providers are supported: Honcho (dialectic reasoning), OpenViking (tiered retrieval), Mem0 (cloud extraction), Hindsight (knowledge graphs), Holographic (local SQLite), RetainDB (hybrid search), ByteRover (CLI-based), and Supermemory.
Messaging Platforms
Ailiv runs as a gateway bot on 27+ messaging platforms, all configured through the same gateway subsystem:
- Telegram, Discord, Slack, WhatsApp, Signal, Matrix, Mattermost, Email, SMS, DingTalk, Feishu/Lark, WeCom, WeCom Callback, Weixin, BlueBubbles, Buzz, QQ Bot, Yuanbao, Home Assistant, Microsoft Teams, Microsoft Teams Meetings, Microsoft Graph Webhook, Google Chat, LINE, ntfy, SimpleX, Open WebUI, Webhooks
See the Messaging Gateway overview for the platform comparison table and setup guide.
Quick connect links
The big platforms have a canonical "create your bot/app" URL, and some accept parameters that pre-open the right form. Skip the console-hunting and go straight there:
| Platform | Direct link | What it opens |
|---|---|---|
| Telegram | t.me/BotFather | Chat with BotFather — send /newbot to mint a bot token |
| Discord | discord.com/developers/applications?new_application=true | Developer Portal with the New Application dialog pre-opened |
| Slack | api.slack.com/apps?new_app=1 | The Create New App dialog — pick From an app manifest and paste the manifest ailiv slack manifest --agent-view generates |
| LINE | developers.line.biz/console | LINE Developers Console for creating a Messaging API channel |
| Feishu/Lark | open.feishu.cn/app | Feishu open-platform console for creating a custom app |
Each platform's setup page walks through what to do once you're there.
Collaboration Workspaces
- Buzz — Block's Nostr-based human+agent workspace. Three integration paths: Buzz Desktop spawns Ailiv as a managed ACP runtime, the
buzz-acprelay bridge hosts a Ailiv identity server-side, or the native gateway platform joins Buzz channels with full Ailiv memory/skills/approvals/cron. The overview page compares all three.
Home Automation
- Home Assistant — Control smart home devices via four dedicated tools (
ha_list_entities,ha_get_state,ha_list_services,ha_call_service). The Home Assistant toolset activates automatically whenHASS_TOKENis configured.
Plugins
- Plugin System — Extend Ailiv with custom tools, lifecycle hooks, and CLI commands without modifying core code. Plugins are discovered from
~/.ailiv/plugins/, project-local.ailiv/plugins/, and pip-installed entry points. - Build a Plugin — Step-by-step guide for creating Ailiv plugins with tools, hooks, and CLI commands.
Training & Evaluation
- Batch Processing — Run the agent across hundreds of prompts in parallel, generating structured ShareGPT-format trajectory data for training data generation or evaluation.