Legba is a disposable browser engine. A real browser, spawned fresh, destroyed on close. No cookies in, no fingerprint left, no trail back. Reach it as an extension, a sandbox, an MCP server, or an API.
Three buyers, one engine. Each gets its own surface.
For fintechs on hardened sites. Banks, brokerages, benefits portals. The sites your users hold accounts on fight automation. Headless tools fail where Legba holds.
site-tuned · sub-15s MFA · persistent state
The extensionFor AI companies shipping agents. Your agent logs in, clicks, and transacts without leaking credentials or getting blocked.
burn per task · no reach · MCP-native
The APIFor security teams mapping exposure. Adversary validates the real exposures: exposed API keys, subdomain takeover, leaked secrets.
validated, not noise · minutes · evidence
AdversaryIsolation, routing, session spawning, and clean exit. No cookies carried in, no fingerprint left behind, no trail back to the operator.
[ how it works ]
Reach Legba through the MCP server, 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.
Pick a geography, scope what the session can reach, set the TTL. The container boots in under 200ms with a real residential IP and a fresh fingerprint.
An agent, a human, or an MCP client takes the wheel. Captchas resolve in-session. MFA codes pull from email forwarding inside 15 seconds. The session sees only what you scoped.
The TTL hits or you close it. The container is destroyed. Cookies, storage, tokens, and fingerprint, all of it gone. Nothing escapes the session because there is no session left.
[ ONE ENGINE. FOUR SURFACES. ]
Legba is one engine with many surfaces. The engine is isolation, routing, session spawning, and clean exit. The surfaces are how different people reach it: an extension, an API, an MCP server, an agent. Every session is fresh, isolated, and deniable. No cookies carried in, no fingerprint left behind, no trail back to the operator.
Same isolation. Same access. Different doors.
A browser tab that runs off your machine. Nothing executes locally. Close it and the session is gone.
See the extensionAGENTSA hosted browser an agent operates inside. It burns on close by default. Real residential IPs and captcha solving baked in.
Meet OpenClawBUILDERSOne config line and any MCP-aware agent gets a real browser. Disposable by default, scoped by you. Claude, GPT, your own.
Get the configBUILDERSA REST API and SDKs over the same disposable browser engine. Spawn sessions in any geography. Persist when you need to, destroy when you do not.
Read the docs
import { Sandbox } from "@legba/sandbox"
const sandbox = await Sandbox.create({
geo: "phoenix-az",
scope: ["legba.app"],
ttl: "15m",
})
await sandbox.agent.run(
"Log in and download my latest statement."
)
await sandbox.destroy()Point the engine at your own surface.
Adversaryspawn latency from a warm pool
reliability over datacenter
session residue on close
Start free. Scale to production. Burn-on-close sessions, residential IPs, and the same anti-bot evasion run across every tier.
Prototype, evaluate, and find us in the MCP registry.
For solo builders and small teams shipping agents to production.
For agent companies and fintechs running at scale.
For multi-product platforms and regulated buyers.
session complete. no trace left.
chromium / real fingerprint · residential ip · burn on close