12 tools · listed in dataset order, no ranking
Developer infrastructure that agents run on, not agents you use directly. The tools here sit at different layers: a model gateway (OpenRouter), ways for an agent to operate a browser, desktop, or phone (Browser Use, Kitesurf, Cua, Opposable), long-term memory (Hindsight), sandboxes and managed runtimes (NVIDIA OpenShell, DigitalOcean Managed Agents, Opengeni), and a voice-agent platform (Vapi). Most projects need one or two of these layers, so start by naming the gap in your agent, then compare the tools that fill it.

OpenRouter
LLM Router and Multi-Provider API Gateway for AI Applications
Best for: Developers building AI applications who want to route across multiple LLM providers, compare model costs, and maintain production reliability through automatic failover without managing separate provider accounts
Vapi
Voice AI Agent Platform
Best for: Developers and enterprises building custom voice agents that need telephony, real-time orchestration, and enterprise security and compliance
Cloudflare
Agent-Native Browser Runtime Without Chromium
Best for: Developers and platform teams running web-browsing AI agents at scale on Cloudflare who want cheaper, higher-concurrency sessions

Browser Use
Browser Use: Open-Source Browser Agent Library, CLI, and Cloud Browser API
Best for: Python developers and AI teams who need an agent to operate real websites, either by embedding the open-source library in their own stack or by renting hosted stealth browsers and agents on usage-based pricing

Vectorize
Hindsight: Open-Source Long-Term Memory for AI Agents
Best for: Developers building agents that must remember users, projects, or their own past work across sessions, who want a framework-agnostic memory service they can self-host or run as managed Cloud
NVIDIA
NVIDIA OpenShell: Open-Source Sandboxed Runtime for AI Agents
Best for: Developers and platform or security teams who run coding or autonomous agents with real file, network, and credential access and want enforceable, reviewable limits outside the agent itself

DigitalOcean
DigitalOcean Managed Agents: Managed Cloud Runtime and Tool Gateway for AI Agents
Best for: Developers and small teams who already use Claude Code, Codex, OpenCode, OpenHands, Hermes, LangGraph, or CrewAI and want those agents running durably in the cloud, with pause, resume, and fork, governed tool access, and usage-based billing in one place

Cua AI, Inc.
Cua: Open-Core Computer-Use Infrastructure for AI Agents on macOS, Windows, and Linux
Best for: Developers who want their existing coding agent to operate native desktop apps without taking over their screen, and AI teams that need reproducible desktops on their own hardware or cloud accounts for computer-use evals, training, and data generation
Cloudgeni
Opengeni: Open-Source, Self-Hostable Runtime for Long-Running AI Agents in Your Product
Best for: Product and platform teams building agent features into their own TypeScript/React product, or running agents for their organization, who want durable sessions, approvals, credential handling, and the choice to self-host under Apache-2.0 or start on a hosted cloud with the same API
Reval Labs
Opposable: Computer Use for Phones, Letting Claude Code, Codex, and MCP Agents Tap and Type in Android and iPhone Apps
Best for: Developers and power users who already run Claude Code, Codex, or another MCP agent and want it to operate real phone apps (2FA codes, banking with approval, messaging, rides) or test their own Android app on a physical device
Omnara
Omnara: Open-Source, Self-Hostable Alternative to Claude Managed Agents for Durable Agents on Any Model
Best for: Product and platform teams that want hosted, long-running agents behind an API, in Slack, or on GitHub, with the freedom to pick any model, run tools on their own machines or third-party sandboxes, and self-host under Apache 2.0 or keep agent history in their own Postgres

Trigger.dev
Trigger.dev: Open-Source Durable Runtime for TypeScript AI Agents and Background Workflows, with Webhook Triggers and Slack and Linear Agents
Best for: TypeScript teams putting AI agents and long-running background jobs into production who want retries, queues, human-approval waits, webhook triggers and tracing without running their own workers, and who may want to self-host later
Model access: OpenRouter gives one OpenAI-compatible API to models from many providers. Acting in the world: Browser Use and Kitesurf give agents a web browser, Cua gives them desktop apps on macOS, Windows, and Linux, Opposable gives them Android and iPhone apps, and Vapi handles phone and voice calls. State: Hindsight stores and recalls what an agent learned across sessions. Where agents run: NVIDIA OpenShell sandboxes agents under file, network, and credential policies, DigitalOcean Managed Agents hosts them in isolated cloud microVMs with a governed tool gateway, and Opengeni is a runtime and control plane for embedding long-running agents in your own product.
Tools in different layers stack rather than compete: one agent can call models through OpenRouter, keep memory in Hindsight, and browse with Browser Use while running inside a sandbox. Real substitutes sit within a layer. Browser Use and Kitesurf both give agents a browser, but Kitesurf is a lightweight, Chromium-free runtime on Cloudflare built for extraction and screenshots, while Browser Use drives a full browser. OpenShell, DigitalOcean Managed Agents, and Opengeni overlap on isolated execution but differ in where they run: your own machine or cluster, DigitalOcean's cloud, or your product.
Fees are structured differently, so model them at your own volume. OpenRouter passes model prices through and charges its fee when you buy credits: 5.5% by card, 5% in crypto, or 8% on its Business plan. Opengeni Cloud adds 5% to model cost. Browser Use's hosted agents bill model cost plus 20%, and its cloud browsers bill per browser-hour. Vapi bills $0.05 per minute for hosting plus your speech, model, and telephony providers. The open-source options (Browser Use's library, Hindsight, OpenShell, Opengeni, Cua's driver) are free to self-host, but you run and maintain them. If your app only ever calls one model from one provider, a gateway adds a dependency without much benefit.
One API for models from many providers
OpenRouter
OpenAI-compatible endpoint with failover and per-model pricing; billed at provider rates plus a fee on credit purchases.
An agent that operates real websites
Browser Use
MIT-licensed Python library you can self-host with any model, or a pay-as-you-go cloud with stealth browsers.
Lightweight page extraction and screenshots at scale
Kitesurf
Cloudflare's Chromium-free browser runtime, free in beta; no persistent logged-in sessions or video and WebGL rendering.
An agent that uses desktop apps
Cua
Open-core driver and sandboxes that let coding agents click, type, and read native apps on macOS, Windows, and Linux.
An agent that finishes a task inside a phone app
Opposable
Exposes an Android phone (iPhone in beta) as MCP tools for Claude Code, Codex, and other MCP clients.
Memory that persists across sessions and users
Hindsight
Open-source memory with retain, recall, and reflect APIs; self-host it or use the pay-as-you-go cloud.
Limiting what a coding agent can touch
NVIDIA OpenShell
Runs agents such as Claude Code or Codex in kernel-isolated sandboxes with YAML policies for files, network, and credentials.
Running existing agents durably in the cloud
DigitalOcean Managed Agents
Isolated microVMs that pause, resume, and fork, plus one MCP endpoint whose tool policies allow, require approval, or deny each call; in public preview.
Embedding long-running agents in your product
Opengeni
Open-source runtime with a replayable event log, approval before risky tool calls, and a self-host or cloud option.
Phone and voice agents
Vapi
Developer platform for voice agents, with your choice of speech, model, and telephony providers.
Editorial framing, not a ranking. Listings on this page are unordered.
Self-hosted open source vs managed service
Self-hosting avoids platform fees and keeps data in your environment, but you operate it: OpenShell needs a recent Linux kernel for its sandbox, and Opengeni's self-hosted stack includes Postgres, Temporal, and NATS. Managed services such as OpenRouter, Vapi, and DigitalOcean Managed Agents trade that work for usage fees.
Convenience vs an extra dependency
A gateway or managed runtime gives you one bill and one integration, but it is another service in the request path that can fail or add latency. Measure it at your expected traffic before relying on it in production.
Agent access vs blast radius
Browser, desktop, and phone control let agents finish real tasks, including in accounts you are signed into. Pair them with isolation and approval controls, such as OpenShell's policies or Opengeni's approval before risky tool calls, and give agents only the credentials a task needs.
Early products vs established services
Several tools here are new: Kitesurf is in beta, DigitalOcean Managed Agents is in public preview, Opposable's iPhone support is in beta, and Opengeni launched publicly in October 2026. Expect pricing and limits to change, and check the vendor's current terms before you commit.
An API layer between your application and model providers such as OpenAI, Anthropic, and Google. You call one endpoint and it routes each request to the model you choose, usually with one bill and failover if a provider is down. OpenRouter is the gateway listed in this category.
Use a gateway when you need to compare model costs across providers, switch providers without refactoring your code, maintain failover routing for production reliability, or restrict which providers can see specific data. Skip the gateway if you only ever call one model from one provider — direct integration is simpler and cheaper.
A gateway is an extra network hop between your application and the provider. OpenRouter says it is built to add as little latency as possible and runs at the edge, and its guide names the cases that add more: cold caches in a new region for the first minutes, a low credit balance that triggers extra checks, and fallback to another provider after a failed attempt. For latency-critical applications, measure it at your expected traffic.
Not to get started, but it limits damage when an agent misreads an instruction or a prompt injection reaches it. NVIDIA OpenShell sandboxes agents on your own machine or cluster with policies for files, network, and credentials. DigitalOcean Managed Agents runs them in isolated cloud microVMs and keeps tool credentials out of the sandbox.
Vapi is a developer platform for building voice agents: you bring or choose the speech, model, and telephony providers and write the backend logic. If you want a ready-made assistant that places calls for you, see ClawCall in the productivity category.
Agent frameworks like LangGraph, CrewAI, and Google ADK define how an agent reasons, calls tools, and coordinates with other agents. The tools here supply what that agent needs around it: model access, a browser or computer to act on, memory, and a safe place to run. A framework-built agent can use several of them at once.
The layer above: frameworks for defining agents that use the gateways, browsers, memory, and sandboxes listed here.
Claude Code, OpenCode, and other coding agents that OpenShell sandboxes and that Cua and Opposable extend to desktop and phone apps.
Vendor facts in this guide last checked October 15, 2026 against: OpenRouter pricing, OpenRouter latency guide, Vapi pricing, Kitesurf docs, Browser Use pricing, Hindsight repository, NVIDIA OpenShell docs, DigitalOcean Managed Agents, Cua, Opengeni pricing, Opposable. Picks and tradeoffs are editorial judgments.