infoconcert.com
partial
Claude Code
intent

What does infoconcert.com do and who is it for? Explain it back to me.

18steps
92.0sduration
$1.4167cost
156,725tokens
21 steps3 reasoning steps13 searches
home
docs
search
search
search
search
/c/info-concert/352131…
/fr/website/infoconcer…
search
search
search
search
search
search
/review/infoconcert.com
search
search
search
40%
on-site discovery
0%
reliability
0%
link following
path origin
  • web search60%
  • prior knowledge40%
insight

The agent could not access infoconcert.com directly due to Cloudflare blocking, so it assembled an answer entirely from web search results and prior knowledge about the company's market position, geographic focus, and business type. While the agent delivered a reasonably coherent overview of what Infoconcert does (European concert discovery platform founded in 1999), it explicitly could not verify pricing, revenue model, or specific features—the core details needed to fully answer three of the four questions in the task. The site's primary pages are inaccessible to agents, forcing reliance on third-party profiles and social media.

  • ›All substantive content came from search result snippets and prior knowledge, not from the site itself. Steps [4], [6], [14], [15], [16], [19] returned only link titles and URLs; the agent inferred company details (founding year 1999, Paris location, 6 employees, 7 countries covered) from search result metadata and cited sources like PitchBook and LinkedIn.
  • ›The site's primary landing page and pricing page both returned Cloudflare 403 responses ([1], [2]), blocking direct access to self-descriptions and pricing tiers. All secondary data sources consulted by the agent (ZoomInfo [10], Similarweb [11], Trustpilot [18]) also returned 403 responses, indicating wide-scale blocking of information aggregator bots.
  • ›The agent had to explicitly acknowledge three major gaps: actual pricing (free vs. paid ticketing, subscription tiers, revenue model), whether users complete purchases on-site or are redirected, and how the platform makes money. These are central to the task ('how it's priced' and 'how it's different from alternatives'), yet no source provided this information.
  • ›Search results occasionally conflated Infoconcert with unrelated products (Koncert, a sales engagement tool) in [5], requiring the agent to disambiguate. The agent correctly filtered these but had no primary source to validate distinctions.
  • ›User reviews on Trustpilot ([17]) were cited as a source but not fetched successfully ([18]). The agent cited Trustpilot as a source in the final answer despite being unable to read it, suggesting it relied on snippet text visible in search results rather than the full page content.

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