The biggest win for me is reliable long-term memory retrieval for agents specifically hybrid search that finds the right user fact even when the memory store is noisy. Concrete example: I bulk-loaded ~500 memories for a test user (mostly filler notes) and planted 6 real facts rice preference, Costa Rica packing details, timezone, reply style, a lamp bulb change, and vendor evaluation notes. Across 3 search rounds, every needle came back at rank 1. That is the feature I care about most: I can store atomic facts once, then ask natural questions later (“how should I respond?”, “what bulb did I put in the bedside lamp?”) and get the right memory without hand-tuning retrieval. How it improved the workflow Instead of stuffing growing chat history into every prompt, I can keep a scoped memory store per user (scope: { type: "user", id: "..." }) and pull only what’s relevant before generating a reply. Batch create (items[]) made load testing and seeding profiles fast — hundreds of memories in ~20–25 seconds in batches of 50. Content deduplication was an unexpected benefit: re-posting the same fact didn’t create junk duplicates, which keeps the store cleaner for agent use. Performance Warm hybrid search felt production-usable (API total often ~20–25ms; client round-trip ~300ms). First queries after a big ingest were slower, then settled quickly. AI / Intelligence The hybrid pipeline (vector + lexical + fact strategies in my runs) is what makes this more than “just embeddings.” Intent classification + ranked results meant preference/style queries and factual queries both worked without me building a custom RAG stack. Integrations / API I mainly used the HTTP API. The OpenAPI surface is clear once you find it, and the mental model is simple: create memories → search → inject into the agent prompt. That’s the loop I’d use regularly in a real product. Pricing / ROI (early view) ROI for me is engineering time saved: not building user-scoped memory, indexing, dedup, and retrieval ranking myself. If you’re shipping a multi-session copilot, that infrastructure is usually weeks of work; Mnemo compresses it to an API call. UI / UX & onboarding (honest note) I didn’t live in the dashboard UI day-to-day value came from the API. Onboarding via the Python SDK/docs was the weaker part (SDK lagged the live API). Once on the correct API contract, the product experience was strong. Bottom line: What I like best is that Mnemo makes “remember this user” a dependable system feature, not a prompt hack — and in my tests, the retrieval quality held up under load.