asur.work
success
Claude Code
intent

What does asur.work do and who is it for? Explain it back to me.

19steps
96.7sduration
$1.4280cost
203,755tokens
30 steps11 reasoning steps11 searches
home
docs
docs
docs
search
/lemma-work/lemma-plat…
search
search
docs.home
search
docs
search
search
search
docs
search
search
search
search
75%
on-site discovery
75%
reliability
50%
link following
path origin
  • previous resource50%
  • web search25%
  • prior knowledge13%
  • other13%
insight

The agent partially satisfied the task by assembling a coherent explanation of what Lemma/asur.work does, who it's for, and how it differs from alternatives—but had to work around missing pricing information and incomplete site documentation. The agent discovered that asur.work is an alias for lemma.work (a runtime for agent-built software) through GitHub and web search rather than from the site itself, and explicitly flagged that the pricing page returns 404, making cost information unavailable. Site navigability was poor: direct URLs returned truncated HTML, the pricing page was broken, and core value proposition details had to be reconstructed from GitHub README and search snippets rather than fetched from the main domain.

  • ›The agent could not retrieve meaningful text from asur.work or lemma.work homepage fetches—all returned truncated HTML that the agent could not parse. This forced reliance on web search and GitHub as the primary sources of truth.
  • ›Step [10] (GitHub repository) and steps [24]–[25] (web search results) were the only content-bearing sources. The GitHub README and search snippets provided the definition ('runtime for agent-built software'), the concept of 'pods', and positioning vs. frameworks. The site itself did not surface these details in a machine-readable way.
  • ›The pricing page (lemma.work/pricing) returns 404 [step 21], leaving a critical information gap. The agent noted 'Free to start with monthly credits' but could not verify specific tiers, costs, or plans from the site. This was the most significant navigability failure.
  • ›The relationship between asur.work and lemma.work was never explained on either domain. The agent had to infer the alias through search results; no canonical redirect or documentation clarifies this.
  • ›The site lacks clear competitive positioning. Search for 'Lemma alternatives' returned unrelated products, and the agent noted no obvious market category or visible customer case studies, limiting ability to contextualize differentiation.
  • ›The agent's final answer heavily weighted GitHub and search snippets over first-party site content, indicating the site did not self-document its value proposition, pricing, or use cases in a discoverable, fetchable form.

Help the next agent finish on asur.work

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 →