lumen.energy
success
Claude Code
intent

What does lumen.energy do and who is it for? Explain it back to me.

20steps
85.8sduration
$1.2201cost
273,898tokens
22 steps2 reasoning steps9 searches
home
docs
docs
search
/solutions
home
/how-it-works
/contact
search
/platform/platform-ove…
/company
search
search
/company/lumen
search
search
search
search
search
docs
64%
on-site discovery
64%
reliability
27%
link following
path origin
  • previous resource27%
  • web search36%
  • prior knowledge36%
insight

The agent assembled a coherent explanation of Lumen Energy by combining fragments from the site's homepage and platform overview with external third-party sources and prior knowledge. The site itself was only partially navigable—many expected pages returned 404s, and critical information like pricing and revenue model was not published in accessible form. The agent had to work around this by citing third-party coverage and making informed inferences.

  • ›Step [1] (homepage) provided the core positioning ('Turn Rooftops Into Revenue', 'modern solar broker') and a concrete usage example ($300K/year for 30,000 sqft building, zero CapEx). Step [3] (about page) reinforced the mission statement and target audience (commercial real estate owners).
  • ›Step [10] (platform overview) was the only site-internal page that delivered substantive operational detail: 'investment-grade solar underwriting', 'portfolio screening', 'competitive bids', 'white-glove execution'. This page was cited in the final response's sources and contained the Lux Engine reference.
  • ›Pricing and revenue model—the hardest part of the task—were almost entirely absent from Lumen's own site. The agent explicitly noted 'specific pricing structure, commission rates, and fees are not publicly disclosed.' Steps [16] and [17] (third-party sources: Facilities Dive and Lowercarbon Capital) provided context on Series A funding and positioning but not pricing details either. The agent had to acknowledge this gap rather than fabricate.
  • ›Site navigation was hostile to agent exploration: /pricing, /how-it-works, /solutions all returned 404s (steps [2], [6], [7]). This forced the agent to rely on prior knowledge for direct URL guessing and pivot to web search to find platform documentation.
  • ›The agent's final framing of 'free to start' and uncertainty about transaction/commission structure is grounded in what the site actually said, not inference. The response correctly flags this as 'confusing' rather than claiming certainty.
  • ›Steps [9], [12], [13], [14], [15], [18], [19], [20] were routing/search steps—they pointed the agent toward resources but the content itself was partial or duplicative. The trajectory shows heavy reliance on web search (36%) and prior knowledge (36%) to compensate for thin site content.

Help the next agent finish on lumen.energy

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →