particle.pro
success
Claude Code
intent
What does particle.pro do and who is it for? Explain it back to me.
6steps
57.9sduration
$0.1065cost
28,727tokens
8 steps2 reasoning steps
home
home
docs
home
home
home
80%
answer from your site
50%
answer efficiency
100%
followed site links
answer sources
- from this site80%
- from agent knowledge20%
url discovery
- given in the task17%
- followed a link83%
insight
The agent successfully gathered comprehensive positioning, pricing, and feature information from Particle's homepage and pricing page. The site exposed most required content directly, though the agent had to re-fetch the homepage multiple times to surface different sections, suggesting incomplete single-page rendering or heavy reliance on model inference to piece fragments into a coherent picture.
- ›Steps [1] and [4] returned overlapping content (homepage fetched 3 times with different response summaries), indicating either client-side rendering requiring multiple requests to surface different sections, or the agent re-querying the same URL hoping to extract different angles. This created inefficiency but also suggests the site doesn't publish a dedicated product overview page.
- ›Step [3] (pricing page) was the only cleanly segmented, complete resource—it alone provided the specific pricing tiers ($29, $399, custom) and per-endpoint costs ($0.003–$0.05). The homepage summaries in steps [1] and [2] mention pricing exists but show 'Loading plans…', indicating the price table may be dynamically loaded and not always captured in full-page fetches.
- ›The agent synthesized competitive positioning (Pod Engine, Listen Notes comparison, MCP uniqueness, blockchain payments) entirely from homepage content in steps [1] and [4], with no dedicated 'Competitors' or 'Why Particle' page linked or discovered. This forced the agent to extract differentiation from feature claims on the main page rather than from a structured comparison or dedicated resource.
- ›Confusions flagged in the final response (x402/MPP blockchain rationale, MCP assumed knowledge, 'earned media' jargon, which endpoints are premium) were NOT resolved by following any site links or fetching additional pages. The agent acknowledged these gaps without attempting to find explanatory docs, suggesting either those docs don't exist or the site structure makes them undiscoverable from the main pages visited.
- ›All 6 fetches were either homepage (memory-typed URL) or the linked pricing page. No breadcrumb navigation, sitemap, docs index, or FAQ was discovered or followed, indicating the site relies on a minimal information architecture that forces users to infer details from sparse homepage content.
See every agent that visits particle.pro
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 →