What does mykutir.in do and who is it for? Explain it back to me.
- previous resource71%
- prior knowledge29%
The agent gathered partial information about myKutir by accessing the homepage, sitemap, and a branding API endpoint, but was unable to extract detailed content due to the site's heavy client-side rendering. The agent successfully identified what myKutir does (AI-powered society management platform for Indian residential complexes) and its core features from page titles and meta descriptions in the sitemap, but could not retrieve pricing information or complete competitive differentiation—the task required explaining the offering to someone else, which the agent accomplished for the 'what' and 'who' dimensions but fell short on 'how it's priced' and concrete 'how it's different' evidence.
- ›Step [1] (homepage) and step [17] (sitemap.xml) revealed the site's information architecture: the sitemap exposed 30+ feature pages (/maintenance-billing-software, /ai-platform, /mobile-app, /help-centre, /pricing, /about, /features, /how-it-works, /contact, etc.), establishing what the platform claims to do via URL slugs and page titles, but actual content remained inaccessible—all returned HTML skeletons with Google Tag Manager / Meta Pixel scripts and no rendered text.
- ›Step [18] (API endpoint /api/platform/branding) was the only truly content-bearing fetch, returning JSON with the company name 'myKutir' and asset URLs—a deliberate API endpoint, but minimal value; all other pages returned identical HTML templates with truncated boilerplate, indicating a React SPA that executes JavaScript to populate content that the agent cannot access.
- ›The agent relied heavily on prior knowledge and web search (29% prior knowledge, 0% web search in sourcing, but turns [7], [8], [14], [15], [24], [25] show search attempts) to fill gaps: pricing, specific differentiators, and competitive positioning were never extracted from mykutir.in itself—all inferences came from competitor research (Mygate, NoBrokerHood) and industry context. The site did not expose pricing despite a /pricing page URL in the sitemap.
- ›Agent-readiness assessment: the site is poorly navigable for automated discovery. The sitemap proved valuable as a directory of intended pages, but the absence of server-side rendering or structured data (ld+json, OG meta tags with content) meant no step beyond the branding API returned actionable content. The agent had to acknowledge this limitation explicitly in its final response ('While the website uses heavy client-side rendering that limits what I can extract directly…').
Help the next agent finish on mykutir.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 →