ora
alpaca.markets
success
Claude Code
intent

What does alpaca.markets do and who is it for? Explain it back to me.

18steps
87.6sduration
$0.1834cost
286,090tokens
23 steps5 reasoning steps4 searches
home
docs
/products
/broker
/broker
docs
docs
search
/broker-reviews/alpaca…
/investing/alpaca-trad…
search
llms.txt
/crypto
/algotrading
search
search
/elite
/stocks
64%
on-site discovery
93%
reliability
43%
link following
path origin
  • previous resource43%
  • web search36%
  • prior knowledge21%
insight

The agent satisfied the task by assembling a comprehensive explanation of Alpaca's business model, pricing, and competitive position from fragmented sources. The main alpaca.markets domain was largely unhelpful (multiple 404s on /docs, /products, /pricing), forcing the agent to rely on the homepage [1], specific product pages (/broker [6], /stocks [16], /crypto [17], /algotrading [18]), an LLMs.txt artifact [15], an /elite page [21], and external review articles [13]. The site publishes key information but does not organize it in a discoverable, unified way—the agent had to guess URLs and supplement with web search and prior knowledge (36% + 21% combined) to construct a coherent narrative.

  • ›The homepage [1] and product pages ([6], [16], [17], [18], [21]) contained positioning and feature descriptions but lacked consolidated pricing, comparison, or audience-targeting information. The agent extracted value from tag lines and product-specific pages rather than from a single 'what-is-alpaca' resource.
  • ›Critical URLs (/docs, /products, /pricing) returned 404s [3], [4], [5], blocking the agent from finding structured documentation or pricing tables. The agent had to discover pages via direct URL guessing (prior knowledge) and search-based discovery ([14]), indicating poor internal navigation architecture.
  • ›The LLMs.txt artifact [15] was discovered via site-specific search and provided a directory of page summaries, but only after the agent had already tried generic paths. This suggests Alpaca publishes machine-readable content but does not expose it via standard navigation.
  • ›External review articles ([13] SmartAsset, and others found via [9], [19], [20] searches) supplied concrete pricing tiers, margin rates, and competitive comparisons that were not clearly stated on the main site. The agent relied on third-party curation to fill gaps in Alpaca's own disclosure.
  • ›The agent correctly identified confusions (market data limitations, API rate limits, Broker vs. Trading API distinction, asset protection details) as gaps in how the site surfaces information—these require reading scattered documentation rather than finding them on main marketing pages.

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 →