Crawl sites, scrape pages, and watch vendor docs for changes from the terminal
Connect WebCrawlerAPI and Luumen can pull public web content into your operational work. Scrape a single page for a synchronous answer, check a crawl job's per-page results and observed costs, or review which monitored feeds detected changes overnight. Starting crawls, creating feeds, and changing feed state are previewed and approved first.
10 tools: 6 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed WebCrawlerAPI run looks like inside Luumen.
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 — create crawl, create feed, delete feed, set feed state — 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 WebCrawlerAPI — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.