Airtop
for LuumenAI

Drive a cloud browser from the terminal, with page changes held for approval

Airtop gives Luumen a cloud browser it can drive. Check which sessions are running, see what each window has open, and ask questions about a page to pull out the details you need. When a check calls for opening a window, navigating somewhere new, or clicking through a page, Luumen shows the step first and waits for your approval. Connected with an API key.

The Airtop toolbox

10 tools: 3 read, 7 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadList SessionsList Airtop browser sessions, optionally filtering by IDs or status.
  • ReadList WindowsList all browser windows in a running Airtop session, including their IDs, current URLs, and titles when available.
  • ReadQuery PageAsk Airtop AI a question about a page or extract structured page content.
  • WriteClick ElementUse Airtop AI to locate an element from a natural-language description and click it. Approval by default
  • WriteClose WindowClose one browser window without terminating its Airtop session. Approval by default
  • WriteCreate SessionCreate an Airtop browser session and wait until it is running. Approval by default
  • WriteCreate WindowCreate a browser window in a running Airtop session and load an initial URL. Approval by default
  • WriteNavigate WindowNavigate an existing Airtop browser window to a new URL and optionally wait for page loading. Approval by default
  • WriteTerminate SessionTerminate an Airtop session and all of its windows. Approval by default
  • WriteType TextUse Airtop AI to locate an input and type text into it. Approval by default

One prompt, start to finish

What a governed Airtop run looks like inside Luumen.

Questions

How does LuumenAI connect to Airtop?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Airtop on its own?

Read actions answer immediately. Anything that writes — click element, close window, create session, create window, and more — is shown as a plan and requires approval by default, including the 4 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Airtop — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Airtop to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.