doc: Broken links fixed in docs (#3034)
This commit is contained in:
@@ -16,8 +16,6 @@ You can enable any of the following modes independently or together:
|
||||
|
||||
Each enhancement can be toggled independently via the `search()` API call. These flags are off by default. These are useful when building agents that require fine-grained retrieval control
|
||||
|
||||
---
|
||||
|
||||
## Keyword Search
|
||||
|
||||
Keyword search expands the result set by including memories that contain lexically similar terms and important keywords from the query, even if they're not semantically similar.
|
||||
@@ -53,7 +51,7 @@ results = client.search(
|
||||
- May slightly reduce precision
|
||||
- Adds ~10ms latency
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Reranking
|
||||
|
||||
@@ -91,7 +89,7 @@ results = client.search(
|
||||
- Adds ~150–200ms latency
|
||||
- Higher computational cost
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Filtering
|
||||
|
||||
@@ -129,7 +127,7 @@ results = client.search(
|
||||
- Adds ~200-300ms latency
|
||||
- Best for focused, specific queries
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Combining Modes
|
||||
|
||||
@@ -148,7 +146,7 @@ results = client.search(
|
||||
This configuration broadens the candidate pool with keywords, improves ordering via rerank, and finally cuts noise with filtering.
|
||||
<Note> Combining all modes may add up to ~450ms latency per query. </Note>
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Performance Benchmarks
|
||||
|
||||
@@ -158,7 +156,7 @@ This configuration broadens the candidate pool with keywords, improves ordering
|
||||
| `rerank` | 150–200ms |
|
||||
| `filter_memories`| 200–300ms |
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Best Practices & Limitations
|
||||
|
||||
@@ -171,6 +169,7 @@ This configuration broadens the candidate pool with keywords, improves ordering
|
||||
|
||||
<Note> You can enable or disable these search modes by passing the respective parameters to the `search` method. There is no required sequence for these modes, and any combination can be used based on your needs. </Note>
|
||||
|
||||
---
|
||||
If you have any questions, please feel free to reach out to us using one of the following methods:
|
||||
|
||||
<Snippet file="get-help.mdx" />
|
||||
|
||||
@@ -19,7 +19,7 @@ You define **criteria** - custom attributes like "joy", "negativity", "confidenc
|
||||
|
||||
This gives you nuanced, intent-aware memory search that adapts to your use case.
|
||||
|
||||
---
|
||||
|
||||
|
||||
## When to Use Criteria Retrieval
|
||||
|
||||
@@ -29,7 +29,7 @@ Use Criteria Retrieval if:
|
||||
- You want to guide memory selection based on **context**, not just content
|
||||
- You have domain-specific signals like "risk", "positivity", "confidence", etc. that shape recall
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Setting Up Criteria Retrieval
|
||||
|
||||
@@ -156,7 +156,7 @@ results_without_criteria = client.search(
|
||||
2. **Score Distribution**: With criteria, scores are more spread out (0.116 to 0.666) and reflect the criteria weights, while without criteria, scores are more clustered (0.336 to 0.607) and based purely on relevance.
|
||||
3. **Trait Sensitivity**: “Rainy day” content is penalized due to negative tone. “Storm curiosity” is recognized and scored accordingly.
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Key Differences vs. Standard Search
|
||||
|
||||
@@ -172,7 +172,7 @@ results_without_criteria = client.search(
|
||||
If no criteria are defined for a project, `version="v2"` behaves like normal search.
|
||||
</Note>
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Best Practices
|
||||
|
||||
@@ -182,7 +182,7 @@ If no criteria are defined for a project, `version="v2"` behaves like normal sea
|
||||
- Avoid redundant or ambiguous criteria (e.g. “positivity” + “joy”)
|
||||
- Always handle empty result sets in your application logic
|
||||
|
||||
---
|
||||
|
||||
|
||||
## How It Works
|
||||
|
||||
@@ -197,7 +197,7 @@ This lets you prioritize memories that align with your agent’s goals and not j
|
||||
Criteria retrieval is currently supported only in search v2. Make sure to use `version="v2"` when performing searches with custom criteria.
|
||||
</Note>
|
||||
|
||||
---
|
||||
|
||||
|
||||
## Summary
|
||||
|
||||
|
||||
@@ -11,34 +11,34 @@ Learn about the key features and capabilities that make Mem0 a powerful platform
|
||||
## Core Features
|
||||
|
||||
<CardGroup>
|
||||
<Card title="Advanced Retrieval" icon="magnifying-glass" href="/features/advanced-retrieval">
|
||||
<Card title="Advanced Retrieval" icon="magnifying-glass" href="advanced-retrieval">
|
||||
Superior search results using state-of-the-art algorithms, including keyword search, reranking, and filtering capabilities.
|
||||
</Card>
|
||||
<Card title="Contextual Add" icon="square-plus" href="/features/contextual-add">
|
||||
<Card title="Contextual Add" icon="square-plus" href="contextual-add">
|
||||
Only send your latest conversation history - we automatically retrieve the rest and generate properly contextualized memories.
|
||||
</Card>
|
||||
<Card title="Multimodal Support" icon="photo-film" href="/features/multimodal-support">
|
||||
<Card title="Multimodal Support" icon="photo-film" href="multimodal-support">
|
||||
Process and analyze various types of content including images.
|
||||
</Card>
|
||||
<Card title="Memory Customization" icon="filter" href="/features/selective-memory">
|
||||
<Card title="Memory Customization" icon="filter" href="selective-memory">
|
||||
Customize and curate stored memories to focus on relevant information while excluding unnecessary data, enabling improved accuracy, privacy control, and resource efficiency.
|
||||
</Card>
|
||||
<Card title="Custom Categories" icon="tags" href="/features/custom-categories">
|
||||
<Card title="Custom Categories" icon="tags" href="custom-categories">
|
||||
Create and manage custom categories to organize memories based on your specific needs and requirements.
|
||||
</Card>
|
||||
<Card title="Custom Instructions" icon="list-check" href="/features/custom-instructions">
|
||||
<Card title="Custom Instructions" icon="list-check" href="custom-instructions">
|
||||
Define specific guidelines for your project to ensure consistent handling of information and requirements.
|
||||
</Card>
|
||||
<Card title="Direct Import" icon="message-bot" href="/features/direct-import">
|
||||
<Card title="Direct Import" icon="message-bot" href="direct-import">
|
||||
Tailor the behavior of your Mem0 instance with custom prompts for specific use cases or domains.
|
||||
</Card>
|
||||
<Card title="Async Client" icon="bolt" href="/features/async-client">
|
||||
<Card title="Async Client" icon="bolt" href="async-client">
|
||||
Asynchronous client for non-blocking operations and high concurrency applications.
|
||||
</Card>
|
||||
<Card title="Memory Export" icon="file-export" href="/features/memory-export">
|
||||
<Card title="Memory Export" icon="file-export" href="memory-export">
|
||||
Export memories in structured formats using customizable Pydantic schemas.
|
||||
</Card>
|
||||
<Card title="Graph Memory" icon="graph" href="/features/graph-memory">
|
||||
<Card title="Graph Memory" icon="graph" href="graph-memory">
|
||||
Add memories in the form of nodes and edges in a graph database and search for related memories.
|
||||
</Card>
|
||||
</CardGroup>
|
||||
|
||||
@@ -26,11 +26,11 @@ Mem0 Platform offers a powerful, user-centric solution for AI memory management
|
||||
|
||||
## Getting Started
|
||||
|
||||
Check out our [Platform Guide](/platform/guide) to start using Mem0 platform quickly.
|
||||
Check out our [Platform Guide](/platform/quickstart) to start using Mem0 platform quickly.
|
||||
|
||||
## Next Steps
|
||||
|
||||
- Sign up to the [Mem0 Platform](https://mem0.dev/pd)
|
||||
- Join our [Discord](https://mem0.dev/Did) or [Slack](https://mem0.dev/slack) with other developers and get support.
|
||||
- Join our [Discord](https://mem0.dev/Did) with other developers and get support.
|
||||
|
||||
We're excited to see what you'll build with Mem0 Platform. Let's create smarter, more personalized AI experiences together!
|
||||
|
||||
Reference in New Issue
Block a user