100tracking.com
partial
Claude Code
intent

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

20steps
97.6sduration
$1.5110cost
209,348tokens
26 steps6 reasoning steps13 searches
home
/en
docs
docs
search
search
search
search
search
/carriers/aramex
search
search
search
search
search
search
search
/faq
/help
search
100%
on-site discovery
43%
reliability
57%
link following
path origin
  • previous resource57%
  • prior knowledge43%
insight

The agent gathered basic information about 100tracking.com (a free, Middle East-focused package tracker supporting 100+ carriers) but could not fully satisfy the task due to the site's JavaScript-heavy architecture and minimal online documentation. The homepage and carrier pages returned only skeleton HTML without rendered content, and critical details about pricing tiers, business features, comprehensive differentiation, and competitive analysis could not be extracted from the website itself—the agent had to assemble its answer largely from prior knowledge and search results rather than direct site inspection.

  • ›Step [1] (homepage) and step [4] (about page) both returned full Next.js skeleton HTML with no text content, script bundles, or structured data—rendering was entirely client-side, making static fetches useless for content extraction.
  • ›Step [14] (carrier-specific page /carriers/aramex) confirmed the site's technical structure but similarly returned no rendered content; the agent could infer existence of carrier support from URL patterns in search results, not from page content.
  • ›The agent relied heavily on prior knowledge (43% sourced) and search engine result snippets to infer what 100tracking does. The Arabic-language meta descriptions in search results were the only source of concrete claims (e.g., 'خدمة تتبع الشحنات المجانية' = free service); the website itself did not directly surface these claims in a fetchable form.
  • ›Multiple 404s (steps [2], [3], [11], [12]) indicated either site structure issues or poor documentation routing; standard discovery paths (pricing, FAQ, help) did not exist or were not indexed.
  • ›Site search (step [13]) surfaced carrier-specific pages but did not reveal documentation, pricing, API details, business tiers, or competitive positioning—the site appears to be tracking-focused with minimal marketing or business intelligence content.
  • ›The agent could not verify the claimed '100+ carriers' count, find any API documentation, confirm a free-forever model, or extract substantive feature differentiation; these gaps were acknowledged in the final response's 'Missing' section.

Want to run your own?

Join the waitlist for early access to point your own agents at any domain, with the intents you choose.

or talk to us about agent readiness →