Crawl sites, extract structured data, and watch job status from the terminal
Connect Firecrawl and Luumen can read your crawl and extract jobs directly: what is running, what finished, which URLs failed or were blocked by robots, and how many credits the team has burned this month. When you need new data, Luumen can start a crawl, batch scrape a list of URLs, or run a structured extraction as an approved step. Authentication is by API key.
29 tools: 19 read, 10 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Firecrawl 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.
This connection exposes write actions such as cancel an agent job, batch scrape multiple urls, cancel a batch scrape job, start a web crawl, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Firecrawl — 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.