MCP
MCP quickstart
Point your agent at the MCP server. It spawns a session and drives a real browser.
Connect the MCP serverDocs
Build on the disposable browser.
Reach the same engine through the MCP server, the API, or the SDK. Spawn a scoped session, do the work, destroy it. Start here, then go deep in the reference.
Quickstart
Three ways in. One engine.
Pick the surface that matches the job. Each one spawns the same disposable browser.
SANDBOX
Sandbox quickstart
Spawn an instance over the API. List images, create, destroy. Three calls.
Read the quickstartAUTH
Auth model
Pass an API key on every request. Scope it per org, rotate it on demand.
See the auth modelLifecycle
Three calls. One throwaway browser.
Spawn a scoped session, do the work, destroy it. The lifecycle is the same through the MCP server, the API, or the SDK. Nothing persists unless you say so.
[ session lifecycle ]
Spawn a scoped session.
Pick a geography, scope the reach, set the TTL. Real residential IP, fresh fingerprint.
Do the work.
An agent, a human, or an MCP client drives. The session sees only what you scoped.
Destroy it.
The TTL hits or you close it. Cookies, storage, tokens, fingerprint: gone on close.
Architecture
A real browser, off your stack.
Every session is a real headful Chromium. Not a headless shell. It renders pages the way a person's browser does, with a real fingerprint and a real residential IP. Sites that block automation see a browser that holds up.
The browser runs off your device and off your stack. Your agent, your code, or your client drives it over the API. Credentials and traffic stay inside the isolated session. Nothing reaches back to your machine or your infrastructure.
The session burns on close. The TTL hits or you destroy it, and cookies, storage, tokens, and the fingerprint go with it. Nothing escapes because nothing is left behind.
Reference
The full API reference.
Every endpoint, with code samples and error shapes. Start with the overview.
- OverviewThe base URL, versioning, and the four surfaces.
- AuthenticationPass an API key on every request. Scope and rotate.
- QuickstartList images, create an instance, make your first call.
- InstancesCreate, list, and destroy browser instances.
- ImagesChoose an operating system and browser configuration.
- KeysInspect your API keys and rotate them on demand.
- LogsRetrieve audit logs for compliance and monitoring.
- ErrorsError codes, response shapes, and what to do next.
- CookbookCommon integration patterns and worked examples.
Access anything.
Expose nothing.
Legba is a disposable real browser: it spawns a clean session, does the work, and destroys itself on close.
chromium / real fingerprint · residential ip · burn on close
Real browser. Real IP. Real page. Spawn a session. Do the work. Destroy it. Off your device. Off your stack. Gone on close.