spur.us
partial
Claude Code
intent

What does spur.us do and who is it for? Explain it back to me.

8steps
47.6sduration
$0.5608cost
30,063tokens
15 steps7 reasoning steps4 searches
home
home
search
docs
docs
search
search
search
0%
answer from your site
0%
answer efficiency
33%
followed site links
answer sources
  • from search results86%
  • from agent knowledge14%
url discovery
  • given in the task25%
  • followed a link25%
  • found via web search50%
insight

The agent provided a substantive explanation of Spur's business despite being rate-limited on the primary domain, assembling a coherent answer from web search results and third-party sources. The site itself was not directly navigable, forcing reliance on external coverage, though search results and third-party comparison pages supplied most needed facts about capabilities, pricing, and positioning.

  • ›The primary domain (spur.us) was entirely inaccessible via HTTP 429 rate limiting on all direct fetch attempts [1, 3, 7, 8], leaving the agent no choice but to pivot to search and external sources.
  • ›Web search [5, 10, 11, 13] surfaced structured information: search result titles and snippets directly answered 'what do they do', pricing tiers, competitors, and founder background without requiring the agent to fetch those third-party pages—the search results themselves were content-bearing.
  • ›Pricing details came entirely from search result snippets [10] and third-party review/comparison sites (Vendr, G2, GoodFirms), not from spur.us/pricing, which the agent could not reach; the agent transparently noted this limitation.
  • ›Competitive positioning and differentiators were extracted from competitor comparison pages [11] (maskbreak.com, G2 alternatives list, ipgeolocation.io blog) rather than Spur's own positioning language, introducing some inference about Spur's strengths relative to named alternatives.
  • ›The agent correctly identified unfetchable content (case studies, SLA guarantees, feature tier details, trial availability) and listed them in a 'Could not find' section, demonstrating awareness of gaps rather than filling them from model memory.

Help the next agent finish on spur.us

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 →