What does here.now do and who is it for? Explain it back to me.
- previous resource75%
- prior knowledge25%
The agent successfully gathered comprehensive information about here.now by fetching the homepage and three key documentation pages (pricing.md, docs.md, index.md), all of which were directly accessible and machine-readable. The site exposed its core messaging, pricing model, and positioning through well-structured markdown files, allowing the agent to synthesize a complete explanation of what here.now does, who it's for, how it's priced, and how it differs from alternatives—though some details (Site Data mechanics, workspace limitations, overage policies) remained under-documented or scattered.
- ›Steps [2], [3], and [4] were all content-bearing and directly cited implicitly through their content appearing in the final response. Step [2] (pricing.md) supplied the detailed freemium tiers and storage limits. Step [3] (docs.md) provided the agent-native positioning and primary job description. Step [4] (index.md) delivered the high-level value proposition, feature list, and use-case guidance.
- ›The site published pricing and positioning in machine-readable markdown at predictable paths (/pricing.md, /docs.md, /index.md), which the agent guessed or retrieved from prior knowledge (75% prior_knowledge + 25% prior knowledge across fetches). This is highly agent-friendly—no JavaScript rendering, no behind-paywalls, no search required.
- ›The agent flagged legitimate gaps: Site Data is mentioned but under-explained; workspace and Drive mechanics are unclear; overage pricing is explicitly withheld ('Do not quote overage pricing'); no competitive comparisons are provided. These are real content gaps, not retrieval failures—the site simply does not document these topics at the level needed for a complete explanation to a third party.
- ›The 75% 'previous_artifact' sourcing suggests the agent leaned on cached or inferred knowledge of here.now's structure rather than discovering pages organically. All four fetches succeeded with 200 status, indicating the site is stable and accessible, but the agent did not need to navigate—it knew where to look.
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 →