Integrations

Connect Twin to your stack

Twin Browser is the browser execution layer your agents call. Reach it over the Model Context Protocol, through LangChain and AutoGen adapters, with OpenAI tool calling, above Playwright, or straight from the REST API — always with one Bearer key.

8 integrationsREST · MCP · LangChain · AutoGenOne Bearer key
Pick an integration

Every path to the same execution layer

The REST API is the universal substrate; everything else is a thin, well-documented wrapper. Compile a task once and reuse it from any of them — skills live at the tenant level.

MCP (Model Context Protocol)

Protocol

MCP is an open protocol that lets an LLM application discover and call external tools over a standard interface. An MCP client (Cursor, Claude Desktop, Claude Code, Cline) connects to an MCP server, lists its tools, and invokes them on the model’s behalf — no bespoke glue per app.

LangChain

Agent framework

LangChain is a Python and JavaScript framework for building LLM applications — chains, agents, and tools. Its agent loop lets a model pick a tool, observe the result, and decide the next action, which makes browser access a natural tool to add.

AutoGen

Agent framework

AutoGen is Microsoft’s framework for multi-agent LLM applications — conversable agents that call registered functions and coordinate to complete a task. Functions registered with an agent become callable tools the model can invoke during a conversation.

Cursor

MCP client

Cursor is an AI-native code editor with a built-in agent that can call MCP tools. Once an MCP server is registered in Cursor’s settings, the agent can invoke its tools while you work — including driving a real browser.

Claude Code

MCP client

Claude Code is Anthropic’s agentic coding tool that runs in the terminal and supports MCP servers. Registered MCP tools become available to the agent so it can take real actions — including browser automation — as part of a coding task.

OpenAI

LLM provider

OpenAI’s API supports function (tool) calling: you describe a function as a JSON schema, the model decides when to call it, and your code executes it and returns the result. This is the standard way to give a GPT-class model access to an external capability.

Playwright

Browser library

Playwright is a browser automation library that drives Chromium, Firefox, and WebKit with explicit, imperative commands — click this selector, fill that field, assert this text. It is precise and fast, but every selector is hand-written and brittle to page changes.

REST API

API

Twin’s REST API is the universal integration path: a small set of HTTPS endpoints under `/api/v1/*` authenticated with a Bearer key. Any language that can make an HTTP request can drive the browser execution layer — no SDK required.

Through any path

What every integration inherits

The cache, replay, and a single auditable key apply no matter how you call in — so the cheapest path is whichever one already fits your stack.

Semantic dispatch cache

Re-phrased goals fuzzy-match a compiled skill, so most calls never re-run the LLM.

Deterministic replay

A compiled skill replays the exact action path with zero LLM calls — from any integration.

One auditable key

Auth, usage-based billing, and an audit log run on every call, whichever path you use.

One key. Every framework.

Spin up a Bearer key and call /api/v1/run from anywhere. Repeated and re-phrased tasks hit the semantic dispatch cache, so your marginal cost per run trends toward zero.