fantastic.jobs
success
Claude Code
intent
What does fantastic.jobs do and who is it for? Explain it back to me.
13steps
72.3sduration
$0.1749cost
171,083tokens
16 steps3 reasoning steps5 searches
home
docs
docs
docs
search
/api
/job-board
/article/best-job-post…
search
search
/lead-generation
search
search
50%
on-site discovery
75%
reliability
25%
link following
path origin
- previous resource25%
- web search50%
- prior knowledge25%
insight
The agent assembled a reasonably complete overview of fantastic.jobs by combining fragments from multiple pages on the site, supplemented by web search results and prior knowledge. The site was partially navigable—core pages like /about, /api, /job-board, and /lead-generation loaded successfully and contained business model information—but critical information like pricing tiers and technical documentation were absent, opaque, or scattered across the domain, forcing the agent to infer details and call out gaps explicitly.
- ›Step [1] (homepage) returned boilerplate Next.js structure but no useful text content; steps [3], [7], [8], [9], [12] all returned similarly opaque HTML (truncated responses with minimal extractable text), indicating the site is heavily client-side rendered and the raw HTML fetches contained little actionable content for the agent.
- ›The agent's richest answers came from web search results (steps [6], [10], [11], [13], [14]), which returned text snippets and inbound article links. The agent cited [fantastic.jobs/about](https://fantastic.jobs/about) as a source but had to synthesize pricing ranges, refresh claims, and use cases from multiple searches and inferences rather than a single authoritative page.
- ›Pricing information was deliberately acknowledged as confused/opaque in the final response—the agent noted the absence of a /pricing page (step [2] returned 404) and the scattered, fragmented nature of pricing data across RapidAPI, Apify, and custom ranges, forcing the agent to warn the user about actual tier gaps and unknowns.
- ›Technical documentation was not accessible on-site (step [4] /docs returned 404); the agent had to note this as missing and infer that customers must contact sales or access it post-signup, reducing transparency.
- ›The agent's ability to deliver a credible answer relied heavily on prior knowledge (25%) and web search (50%) rather than direct site fetches (25%), indicating the site did not publish its value proposition, business model, or competitive positioning in a machine-readable or easily scrapable form.
Help the next agent finish on fantastic.jobs
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 →