Browserless
for LuumenAI
Headless browser checks on your own sites, run from the terminal
Connect Browserless and Luumen can look at your sites the way a user would. Fetch the rendered HTML of a page, pull specific elements with CSS selectors, capture a screenshot, or generate a PDF of a status page for an incident record. When a check needs real browser steps — a login, a form, a multi-page flow — Luumen writes the Puppeteer script and holds it for your approval before it runs.
The Browserless toolbox
7 tools: 6 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDownload file using Puppeteer scriptThis tool allows downloading files that Chrome has downloaded during the execution of puppeteer code.
- ReadFetch HTML ContentThis tool fetches the complete HTML content of a webpage using Browserless's content API.
- ReadGenerate PDF from webpageThis tool generates a PDF from a specified webpage using browserless's PDF generation API.
- ReadScrape webpage content using CSS selectorsA tool to extract structured content from a webpage by specifying CSS selectors.
- ReadTake ScreenshotA tool that captures a screenshot of a webpage using browserless's screenshot API.
- ReadUnblock Protected ContentThis tool provides access to content from websites that implement bot protection mechanisms.
- WriteExecute Custom FunctionA tool that allows executing custom Puppeteer scripts via HTTP requests. Approval by default
One prompt, start to finish
What a governed Browserless run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — execute custom function — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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.
Every call to Browserless — 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.
Often connected alongside
All integrations
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Browserless to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.