postonus.com
partial
Claude Code
intent

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

19steps
111.9sduration
$1.3060cost
257,694tokens
32 steps13 reasoning steps8 searches
home
docs
/en/pricing
/features
/en/features
search
search
/api
search
docs
search
docs
search
search
search
docs
/help
search
sitemap
100%
on-site discovery
82%
reliability
27%
link following
path origin
  • previous resource27%
  • prior knowledge73%
insight

The agent assembled a partial understanding of Postonus by extracting metadata from the sitemap and citing it alongside prior knowledge and failed fetch attempts. The site is built in NextJS with client-side rendering, which prevented the agent from accessing the actual feature lists, detailed pricing tiers, and platform support details that would have been visible in a browser—leaving critical gaps in the explanation despite confident positioning claims.

  • ›Step [29] (sitemap.xml) was the only content-bearing fetch that returned structured, machine-readable data. It confirmed the existence of /en, /en/pricing, /en/features, /en/blog, /en/docs, /en/api, and /en/changelog pages, but provided no content from those pages themselves.
  • ›Steps [1–4], [8], [15], [20–21], [30] fetched actual pages (/pricing, /features, /docs, /api, /blog) but all returned HTML skeletons with NextJS placeholders and truncated responses. The agent could not extract visible text, feature lists, or pricing details from these responses—only metadata tags in the <head>.
  • ›The agent's final answer relies heavily on prior knowledge (73% per the run report) and inferences from page titles and metadata rather than content extraction. Claims about '13 features', specific pricing ($12/month), and platform logos come from meta descriptions and prior knowledge, not from successfully rendering the pages.
  • ›Web searches [7], [10–11], [13], [18], [23], [25], [27] returned no results for 'Postonus' itself—only competitors (Buffer, Hootsuite, Postiz, Postpone). This suggests either very low search visibility or that the agent/search engines cannot index the site effectively.
  • ›The agent explicitly acknowledged in its final response that 'the NextJS page rendering prevented me from seeing the complete list' and 'the NextJS-rendered pages prevented me from seeing full feature lists, detailed pricing tiers,' confirming the core friction point.
  • ›Despite the incomplete access, the agent constructed a plausible narrative (developer-first, API/CLI/MCP emphasis, sub-$20 pricing) and positioned Postonus as differentiated from traditional social media tools. This narrative is not verifiably wrong, but it is not grounded in fetched content—it is an educated guess based on fragments.

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