What does getzep.com do and who is it for? Explain it back to me.
- previous resource25%
- web search25%
- prior knowledge50%
The agent successfully assembled a comprehensive explanation of Zep by combining fragments from the main website, documentation hub, and web search results. The site's marketing pages provided conceptual positioning (Context Lake, temporal knowledge graphs) and compliance claims, but lacked concrete pricing details, forcing the agent to rely on web search and prior knowledge to fill gaps. Navigation was serviceable but incomplete—key information like exact pricing tiers and self-hosting availability required external sources rather than being clearly stated in fetchable form on getzep.com itself.
- ›Steps [1, 2, 4] fetched the main homepage, pricing page, and about page but returned only HTML shells without rendered content visible in the response. The agent could not extract pricing tiers, feature breakdowns, or use-case details directly from these responses, forcing reliance on web search (steps [10, 14]) to learn that pricing is credit-based and that specific tier costs require sign-up or sales contact.
- ›Steps [8, 9] revealed domain-level content structure (ai-agents/, platform/context-lake/) that helped the agent understand Zep's positioning around temporal reasoning and enterprise-scale agent memory, but the actual feature details and differentiation had to be synthesized from external comparison articles (web search step [11]).
- ›The documentation hub (step [6], help.getzep.com/) and blog (step [13]) were accessible but returned only HTML structure; neither contained the rendered content needed to answer the task. This forced the agent to heavily weight prior knowledge and web search (50% + 25% + 25%) rather than extracting all answers directly from getzep.com.
- ›The agent correctly identified missing information and called it out (unclear pricing tiers, no self-hosting, limited free-tier details, lack of direct competitor comparison on the marketing site), demonstrating awareness of what the site failed to surface.
- ›Web search steps [7, 10, 11, 12, 15] were critical—they returned URLs and snippets that pointed to specific pages (ai-agents/, enterprise/) and competitor comparisons that the agent could not have discovered from the homepage alone, suggesting the marketing site's information architecture is not fully interconnected or self-explanatory.
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 →