docs: remove temporal examples from memory API reference

This commit is contained in:
agumpandey
2026-05-12 23:54:02 +05:30
parent b2b36147ba
commit d1f5cc9f64
2 changed files with 0 additions and 37 deletions
@@ -70,7 +70,3 @@ memories = client.get_all(
<Info>
The response is a paginated envelope with `count`, `next`, `previous`, and `results`. Use `page` and `page_size` query params to step through results.
</Info>
<Note>
`get_all` is best for exports, audits, and raw record inspection. Use <a href="/api-reference/memory/search-memories">Search Memories</a> when you want time-aware ranking or query interpretation.
</Note>
@@ -18,10 +18,6 @@ The `filters` object supports complex logical operations (AND, OR, NOT) and comp
- `icontains`: Case-insensitive containment check
- `*`: Wildcard character that matches everything
## Temporal reasoning in V3 responses
Temporal Reasoning is applied internally during retrieval. Search responses keep the normal result shape.
### Search parameter defaults
| Parameter | V1/V2 | V3 |
@@ -67,35 +63,6 @@ related_memories = client.search(
```
</CodeGroup>
### Temporal query example
<CodeGroup>
```python Platform API Example
results = client.search(
query="what did I do last week?",
filters={"user_id": "alice"},
reference_date="2025-03-21T00:00:00Z",
)
```
```json Output
{
"results": [
{
"id": "9b59b0fd-0b31-4a0b-a3ad-7f26bb4f1f8d",
"memory": "Finished the Q1 product review on March 10, 2025.",
"user_id": "alice",
"score": 0.91,
"metadata": {},
"categories": [],
"created_at": "2025-03-10T00:00:00Z",
"updated_at": "2025-03-10T00:00:00Z"
}
]
}
```
</CodeGroup>
<CodeGroup>
```python Wildcard Example
# Using wildcard to match all run_ids for a specific user