Integrations
Providers, Placet, channels, MCP servers, skills, scripts, browser work, and credentials.
Facio is designed to be extended while it is running. The runtime can work with different model providers, channels, tools, MCP servers, skills, scripts, browser work, and credentials without reducing everything to one static startup configuration.
Use this page to understand the integration surface at a practical level.
Provider routing
Facio supports commercial, local, and OpenAI-compatible model endpoints. The public product idea is simple: pick the provider that fits the current job, cost, latency, and capability needs.
| Provider area | Examples | Typical reason to use it |
|---|---|---|
| Hosted LLMs | OpenAI, Anthropic, OpenRouter, Azure OpenAI, GitHub Copilot | Strong general capability and managed infrastructure. |
| Local/runtime endpoints | Ollama, LM Studio, vLLM, OpenAI-compatible endpoints | Local evaluation, data-control experiments, or custom model hosting. |
| Per-task routing | Main agent and subagent routing | Use a stronger model for hard reasoning and a cheaper route for routine work. |
For practical setup fields, API keys, base URLs, OAuth providers, and local model routing, continue with Providers.
Placet-first workflow
Placet is the primary operator surface. It is where Facio fits best when the workflow needs approvals, files, forms, progress states, and management controls.
Other channels are useful for reach, but Placet is the clearest place to supervise work that has real side effects.
Channels
Facio can be reached through several transports:
- Placet for full operator workflows.
- Telegram, Slack, Discord, Email, and Microsoft Teams for team communication.
- CLI for local operator use.
- OpenAI-compatible HTTP and A2A for API-style integration.
Every enabled channel should have an explicit access rule. An empty allow list denies access; use * only when anonymous access is intentional.
Channel-specific fields are documented in Channels.
Tools and protocols
Facio can use multiple tool categories:
| Tool type | What it enables |
|---|---|
| MCP servers | Add external tool servers over supported transports without baking every tool into the core runtime. |
| Skills | Package reusable workflows and instructions for recurring tasks. |
| Scripts | Run controlled helper logic for tasks that are better expressed as code. |
| Browser and web | Fetch, inspect, search, and reason about web information. |
| Media tools | Work with attachments, transcription, images, and video where configured. |
| Shell/file tools | Inspect and modify workspace files under policy and sandbox constraints. |
Credentials
Credentials should be scoped to what the task actually needs. Facio is designed so the agent can reference a secret through a placeholder while the runtime resolves it at the boundary where it is needed.
Operationally, this means:
- Do not paste secrets into prompts, docs, skills, or channel messages.
- Use scoped credentials for skills, channels, providers, and tools.
- Expose credentials to shell commands only when a CLI really needs them.
- Review which integrations can create external side effects.
For the concrete credential store, provider credential API, password placeholders, and MCP linking behavior, see Configuration Credentials and MCP Credentials.
Integration rollout
Start small:
- Configure one provider.
- Run a low-risk task in Placet.
- Enable one additional channel or tool category.
- Confirm logging, approval, and credential behavior.
- Add broader integrations only after security and operations are clear.