escavador.com
partial
Claude Code
intent
What does escavador.com do and who is it for? Explain it back to me.
5steps
36.0sduration
$0.0160cost
28,059tokens
8 steps3 reasoning steps1 search
home
home
search
/precos
/hc/pt-br/articles/506…
33%
answer from your site
25%
answer efficiency
33%
followed site links
answer sources
- from this site33%
- from search results17%
- from agent knowledge50%
url discovery
- given in the task25%
- followed a link25%
- found via web search50%
insight
The agent could not access the main domain directly but assembled a usable overview from the support center and search snippets. The site's 403 blocks on the homepage and pricing page forced reliance on secondary sources, leaving prices unverified and key details (free-tier limits, feature coverage, AI accuracy claims) undocumented on accessible pages.
- ›Both escavador.com/ and www.escavador.com/precos returned HTTP 403 Forbidden, making the main site inaccessible; agent resorted to support center and search-snippet assembly.
- ›The support center article (step [6]) provided core service descriptions, use cases, and data sources, but omitted pricing, free-tier limits, and feature list details.
- ›Search results (step [3]) yielded pricing info only as snippets, never fetched directly; agent notes prices as unverified and warns the user to check the official site.
- ›Agent correctly identified conflicting plan counts across sources (support lists 3; search snippet includes Business tier) and flagged the discrepancy.
- ›Agent transparently acknowledged it could not verify differentiation claims, did not open the third-party comparison link, and did not fill gaps with unsourced assertions—strong epistemic discipline despite partial task completion.
Help the next agent finish on escavador.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 →