Skip to main content
For AI agents

Disposable browser infrastructure for AI agents.

A real headful Chromium on a fresh residential IP. Spawned per task, destroyed on close. Your agent logs in, clicks, and reads the rendered page, then the browser is gone.

Get startedRead the docs

One engine. Three jobs.

Your agents need routing and isolation. Legba provides both through a ready skill.

A keyed session cartridge lifts from its docking cradle.

A separate browser for every task.

Run each task in an isolated browser. The browser is destroyed when the session closes.

A physical rail switch selects between two private routes.

A private route for your browser.

Connect through the agent skill or a proxy endpoint. Use a private route for browser traffic.

A monitor displays a rendered page beneath a moving inspection lens.

A rendered page your agent can read.

Chromium renders the page, including its layout and images. Your agent reads the page and interacts with it.

[ session lifecycle ]

Spawn it. Use it. Destroy it.

Reach the engine over MCP, the API, or the SDK. The lifecycle is the same every time. Spawn a scoped session, do the work, destroy it. Nothing persists unless you say so.

[ session lifecycle ]

  1. Spawn a scoped session.

    Your agent calls spawn. Pick a geography, scope the reach, set the TTL. A real Chromium boots on a fresh residential IP. Nothing from the last run is carried in.

  2. Do the work.

    The agent drives over MCP, the API, or the SDK. It navigates, clicks, types, and reads the rendered page. The session sees only what you scoped.

  3. Destroy it.

    The TTL hits or the agent closes the session. Cookies, storage, tokens, and fingerprint go with it. Nothing escapes because nothing is left.

Where to go next.

Choose the skill, read the docs, or compare plans.

A hinged bridge opens and closes between two arched supports.

Connect your agent.

Use routing and isolation through the agent skill.

Talk to us about the skill
A drafting scroll unrolls to reveal an architectural drawing.

Read the docs.

Setup, examples, and the public reference.

Open documentation
A mechanical caliper opens its sliding jaw along a graduated beam.

Find your plan.

Compare plans for your agent workload.

Compare agent plans
FAQ

Common questions.

Why do agents need a separate browser?
Each task gets its own isolated browser. A shared profile can leak cookies and tokens between agents. Legba destroys the browser when the run ends.
Does it work with my framework?
Agents drive Legba over MCP, the API, or the SDK. They navigate, click, type, and read the rendered page. Use the interface that fits your stack.
Why does headful rendering matter?
A real Chromium renders pixels, layout, fonts, and images. Vision models read what a person would see. Headless browser signals never reach the site.
What persists between runs?
By default, nothing persists between runs. Cookies, storage, tokens, and fingerprints are destroyed. Persistent state is explicit and opt-in.
How is it priced?
It is free to prototype. The next tiers are Pro, Production, and custom Enterprise. See cloud API pricing for current details.

Use the internet without the internet using you.

Legba is a Chrome extension with two modes. Ghost gives you a private browser route. Shield opens a page in an isolated browser off your device.

Add to Chrome

Free for 30 days. No card required.

Ghost. A private route for your browser. Shield. An isolated browser, off your device. Choose the mode. Close when finished.