staging.trade-form.com
success
Claude Code
intent

What does staging.trade-form.com do and who is it for? Explain it back to me.

11steps
37.5sduration
$0.2978cost
108,151tokens
18 steps7 reasoning steps
home
docs
docs
llms.txt
/product
/product.md
docs
/developers.md
/about.md
/index.md
.well-known
100%
on-site discovery
100%
reliability
91%
link following
path origin
  • previous resource91%
  • prior knowledge9%
insight

The agent successfully assembled a comprehensive explanation of TradeForm by fetching the homepage, markdown documentation files, and the llms.txt artifact. The site was well-navigable and published structured, machine-readable content (.md files with metadata and full copy) that directly answered what TradeForm does, who it's for, how it's priced, and how it differs from alternatives. The agent identified genuine gaps in publicly available information—particularly around competitive positioning, pricing tier details, and implementation scope—which reflect intentional product strategy (consultative sales model), not missing navigation.

  • ›The core answer came from fetched markdown files (index.md, product.md, pricing.md, about.md, developers.md) and llms.txt, all of which were directly fetchable and contained rich, complete copy including founding story, value proposition, pricing starting point, and technical positioning.
  • ›The site published its content in agent-friendly formats: structured .md files with metadata, an llms.txt file that explicitly indexes pages and use cases, and canonical URLs. The agent did not have to scrape or parse HTML; markdown sources were directly available and contained the full narrative.
  • ›Several confusions the agent noted (opaque Scale plan pricing, lack of competitor names, feature-depth ambiguity, ROI quantification) are genuine gaps in published content, not navigation failures. The site intentionally withholds these details, directing inquiries to team@trade-form.com. This is a business choice, not a site usability problem.
  • ›The agent relied heavily on prior knowledge for only ~9% of fetches; 91% came from previous artifacts (cached .md files and llms.txt), indicating the site's content was stable and re-fetchable, not dynamically rendered or behind auth.
  • ›Developer resources (developers.md) revealed a secondary positioning angle (agents as API consumers via OpenAPI/MCP/CLI) that was mentioned but not emphasized in marketing copy—this required cross-referencing multiple pages to surface.

See every agent that visits staging.trade-form.com

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 →