ora
alkali.engineering
success
Claude Code
intent

What does alkali.engineering do and who is it for? Explain it back to me.

8steps
55.5sduration
$0.1075cost
34,963tokens
12 steps4 reasoning steps2 searches
home
home
home
home
search
/companies/alkali
search
docs
67%
answer from your site
17%
answer efficiency
60%
followed site links
answer sources
  • from this site67%
  • from external pages17%
  • from agent knowledge17%
url discovery
  • given in the task17%
  • followed a link50%
  • found via web search17%
  • guessed the URL17%
insight

The agent successfully assembled an explanation of Alkali's core offering, target market, and positioning from their homepage, but identified a critical gap: pricing is completely absent from the site. The agent filled competitive context using external sources and search results, but the site itself surfaced no pricing information or competitive comparisons.

  • Step [1] yielded complete product description, capabilities, and market position from the homepage alone; no deeper site navigation was needed or surfaced for core features.
  • Pricing is genuinely absent from alkali.engineering — steps [2], [3], [4], [5] all searched the site via direct URL guesses and re-fetches of the homepage, finding no pricing page or cost disclosure, indicating the information is not published anywhere on the domain.
  • The Y Combinator result (step [8]) created confusion because it refers to a different Alkali company in chemical engineering, not steel estimation — a misdirect that the agent correctly flagged but which showed that search results introduced false positives without site-level disambiguation.
  • Competitive positioning was entirely absent from site content; the agent had to resort to external research (steps [7], [10]) to contextualize Alkali against Tekla PowerFab, StruMIS, and SDS2, proving the site makes no effort to position itself relative to alternatives.
  • The site published all substantive claims about what Alkali does via its homepage in a single fetch; the agent's subsequent re-fetches of the same URL yielded identical content in different reframings, suggesting limited site depth or navigation options for the target task.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →