What does drishtisignals.in do and who is it for? Explain it back to me.
- previous resource90%
- prior knowledge10%
The agent successfully gathered a comprehensive overview of Drishti Pro's purpose, audience, and positioning, grounded primarily in fetched content and one API response. The site proved moderately navigable: core pages (about, contact, live dashboard, developers) were accessible and content-bearing, but pricing information was genuinely absent (not hidden), and the homepage relies heavily on JavaScript that static fetches cannot render. The agent correctly inferred the free model from the absence of a pricing page and the public visibility of signals, then supplemented with web searches to contextualize competitors—though those searches did not return Drishti-specific pricing details, confirming the model's transparency rather than failing to find hidden information.
- ›Step [6] (api/stats.json) delivered machine-readable proof of the core claim—62.1% win rate across 743 signals with full ledger breakdown—making the site's transparency verifiable and directly answerable without interpretation.
- ›Steps [3], [5], [7], [11] (about, contact, live, developers pages) all returned rich content describing the product, its integrations, track record, and API surface; these were discoverable via standard site navigation and contained the identity/positioning information needed.
- ›Step [1] and [10] (homepage) returned JavaScript-heavy HTML that truncated during static fetch, obscuring the full interface and marketing messaging; the agent worked around this by navigating to specific pages rather than extracting from the homepage, suggesting the site's information architecture compensates for this limitation.
- ›Pricing information was genuinely absent—not buried or obfuscated—confirming the free model is a core design choice rather than a discovery failure; the agent correctly inferred this and explained it.
- ›The site did not require authentication, API keys, or special access to understand its offering, and published live data via a public JSON endpoint, making it highly agent-readable for data retrieval; the main friction was JavaScript rendering on the homepage, not access control.
- ›Web searches [8, 12, 14, 15] did not yield Drishti-specific pricing or comparison information, which is consistent with the site's minimal marketing and transparency-first positioning rather than indicating navigation failure.
See every agent that visits drishtisignals.in
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 →