Browseai
for LuumenAI
Run Browse.ai robots, check task history, and set up change monitors
Browse.ai turns websites into structured data through recorded robots. Connect it with an API key and Luumen can list your robots, read task history, check the Browse.ai task queue, and see which webhooks are wired up. When something needs to change — a re-run, a new monitor, a webhook — Luumen shows the plan first and waits for your approval.
The Browseai toolbox
11 tools: 5 read, 6 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Robots ListRetrieves a list of all robots (automated web tasks) under your Browse AI account.
- ReadGet Robot TasksRetrieves a paginated list of all tasks (execution runs) for a specific Browse AI robot.
- ReadGet System StatusCheck the operational status of Browse AI infrastructure, including the tasks queue condition.
- ReadGet Task DetailsRetrieves detailed information about a specific Browse AI task by robot ID and task ID.
- ReadList Robot WebhooksRetrieve all webhooks configured for a specific Browse AI robot.
- WriteBulk Run TasksThis action allows users to bulk run up to 1,000 tasks per API call using a specified robot. Approval by default
- WriteCreate MonitorCreates a new monitor for a Browse AI robot to automatically track website changes over time. Approval by default
- WriteCreate WebhookThis tool creates a new webhook for a Browse AI robot. Approval by default
- WriteDelete a specific monitorThis tool allows users to delete a specific monitor from their Browse AI account. Approval by default
- WriteDelete a specific taskThis tool allows you to delete a specific task in BrowseAI by its task ID. Approval by default
- WriteRun RobotTriggers the execution of a Browse.ai robot to extract data from websites. Approval by default
One prompt, start to finish
What a governed Browseai 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 — bulk run tasks, create monitor, create webhook, delete a specific monitor, and more — is shown as a plan and requires approval by default, including the 2 actions 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 Browseai — 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
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put Browseai to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.