tapir-app.com
success
Claude Code
intent

What does tapir-app.com do and who is it for? Explain it back to me.

20steps
94.3sduration
$1.3493cost
242,945tokens
26 steps6 reasoning steps6 searches
home
docs
/features
docs
/tarifs
/tarifs
home
search
search
/a-propos
search
/en
search
docs
search
/doc
/ressources
/api
/widgets
search
100%
on-site discovery
36%
reliability
57%
link following
path origin
  • previous resource57%
  • prior knowledge43%
insight

The agent partially satisfied the task by assembling a coherent explanation of Tapir's core offering, pricing, and positioning—but had to work around a French-primary website with minimal English content and a sparse page structure. It successfully retrieved the homepage (steps 1, 12), pricing page in French (steps 7, 9), and About page (step 16), extracting key information like the pay-per-use model (€2 per file + €1 for AI review), document collection workflow, and company attribution (Coding Spark, Montpellier). However, the agent could not access most standard pages (/pricing, /features, /blog, /docs returned 404s), and had to rely partly on prior knowledge and web search results to contextualize competitors and differentiation—a sign the site does not publish comparative or detailed feature information in a machine-readable form.

  • ›Step 7 and 9 returned the /tarifs page successfully (200), which was the primary source for pricing details (€30 credit, €2/file, €1/AI review)—found by the agent guessing a French-language URL after /pricing failed, indicating the site reserves pricing info for French path only.
  • ›Step 1, 12, and 16 returned homepage and About page HTML, but the agent noted heavy Next.js client-side rendering truncated responses; extracted content was sparse, forcing reliance on prior knowledge (57%) to synthesize the final answer about target users, AI-assisted review workflow, and lack of account friction.
  • ›The site's navigation is minimal: most standard pages (features, blog, docs, API docs) return 404s, and there is no English version accessible via /en. The agent had to guess multiple French-language paths (/a-propos, /tarifs) and ultimately resorted to web search (steps 13, 15, 17, 19, 24) to fill gaps on competitors, integration details, and broader positioning—a sign the site is not agent-optimized for discovery of these questions.
  • ›The agent explicitly cited sources [Tapir Homepage, Pricing Page, About Page] in its final response, confirming steps 1, 7/9, and 16 were the content-bearing paths used; web searches were used for contextualization but not for direct facts about Tapir itself.
  • ›The site's lean, early-stage design (minimal documentation, no blog, no public competitor positioning) makes it harder for agents to extract complete answers without prior knowledge or external searches. Critical information (pricing, company background, use cases) exists but is scattered across French-only pages.

Help the next agent finish on tapir-app.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 →