Integrations

Integrations connect Everruns agents to external services, cloud sandboxes, browsers, search providers, and messaging channels. Tool integrations surface as capabilities. Messaging integrations use endpoints owned by the Agent.

Sandboxes & execution

Give agents an isolated environment to run code, edit files, and persist state.

Integration	What it provides
Daytona	Cloud sandbox environments via the Daytona REST API
E2B	Cloud sandboxes via the E2B management + runtime APIs (bring your own key)
Container Sandbox	Self-hosted container sandboxes via Docker Engine, no external SaaS
Sprites	Persistent Firecracker microVMs with checkpoints and HTTP services
Cursor	Launch and manage asynchronous Cursor Cloud coding agents

Browser & web

Integration	What it provides
Browserless	Cloud browser automation, screenshots, DOM, scraping, multi-step flows
Brave Search	Web search via the Brave Search API
DuckDuckGo	Instant answers via the DuckDuckGo API
Parallel	Web search, extract, and task APIs (free and paid tiers)

Reasoning & judgment

Integration	What it provides
TypeSafe	Typed judgments: probabilities, single-choice routing, graded scores

Agents on the OpenRouter provider can also get web reach without a separate integration via the OpenRouter Server Tools capability (web_search, web_fetch), which OpenRouter executes server-side.

Messaging channels

Integration	What it provides
Slack	Deploy an Agent as a Slack bot through an endpoint

Credentials

Guide	What it provides
Secure MCP Credentials	Write-only Agent credential bindings for secret MCP tool parameters

Discovery

Integration	What it provides
ARD	Client-side discovery of external MCP servers and A2A agents at runtime

Model providers

Integrations connect agents to tools and services. Providers connect Everruns to the AI model vendors that run your agents, OpenAI, Anthropic, Google Gemini, AWS Bedrock, OpenRouter, and more. See the Providers overview to configure one.

Adding an integration

New integrations follow a parity checklist (connection provider, tests, live-API coverage, docs, and a threat-model section) before they ship. Daytona is the reference implementation. See the in-repo knowledge/integrations/integrations.md for the full contract.