ninethirty.ai
partial
Claude Code
intent
What does ninethirty.ai do and who is it for? Explain it back to me.
30steps
135.2sduration
$1.8004cost
650,443tokens
35 steps5 reasoning steps11 searches
home
docs
/features
docs
search
/screener
search
/@austin-starks/i-anal…
search
docs
docs
docs
/backtesting
search
/help
search
search
docs
docs
search
search
search
/signup
sitemap
sitemap
/about-us
docs
/drmarket
search
search
79%
on-site discovery
68%
reliability
42%
link following
path origin
- previous resource42%
- web search21%
- prior knowledge37%
insight
The agent assembled a partial understanding of ninethirty.ai by fetching its homepage, pricing page, screener page, blog, docs, about-us page, and drmarket page—but was unable to retrieve usable content from any of these fetches due to heavy JavaScript rendering. The agent relied heavily on prior knowledge (37%) and web search results (21%) to construct its explanation, ultimately unable to verify key claims (pricing, specific features, competitive positioning) directly from the site itself.
- ›All 200-status fetches from ninethirty.ai returned truncated HTML boilerplate (fonts, scripts, gtag) with no visible rendered content in the response bodies—indicating the site is client-side rendered and the agent could not extract feature or pricing information from raw HTML.
- ›The agent successfully located the sitemap index and static sitemap, which revealed the existence of pages like /about-us/, /pricing/, /pricing/alpha/, and /drmarket/, but fetching these pages yielded no actionable content.
- ›Pricing information remains entirely absent from the agent's final answer—the agent acknowledges it 'could not find clear pricing information' and had to note pricing as a confusing gap. This is a critical failure for the stated task goal of explaining 'how it's priced.'
- ›The agent had to rely on external third-party comparisons (WallStreetZen, Webull blog) and prior knowledge about the founder (Austin Starks) to construct a coherent narrative—the site itself did not publish this information in a form the agent could retrieve.
- ›The agent explicitly noted that ninethirty was 'not prominently featured' in comparative articles, suggesting weak market visibility, but this observation came from web search results, not from the site's own positioning.
- ›The site's navigation structure was navigable (sitemap was present, URLs were guessable), but the rendering barrier made actual content discovery impossible—a heavy JavaScript rendering wall converted a structurally sound site into an agent-hostile one.
Help the next agent finish on ninethirty.ai
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 →