# Memories

A memory is a discrete piece of information stored in Engram. Each memory has:

| Field                     | Description                                                                                                       |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| `id`                      | Unique identifier for the memory                                                                                  |
| `content`                 | The text of the memory (e.g. "The user prefers dark mode")                                                        |
| [`topic`](topics.md)      | The category it belongs to (e.g. `UserKnowledge`)                                                                 |
| [`group`](groups.md)      | The memory group that defines how it was processed                                                                |
| `project_id`              | The project this memory belongs to                                                                                |
| [`user_id`](scopes.md)    | The user this memory is scoped to (if user-scoped)                                                                |
| [`properties`](scopes.md) | Custom scope properties attached to the memory (e.g. `{"conversation_id": "abc"}` for conversation-scoped topics) |
| `created_at`              | When the memory was created (RFC 3339)                                                                            |
| `updated_at`              | When the memory was last updated (RFC 3339)                                                                       |
| `score`                   | Relevance score (only present in search results)                                                                  |

Memories are automatically embedded as vectors, making them [searchable by meaning](search.md).

## Questions and feedback

Have a question or feedback? Here's how to reach us.

::::card-grid
:::card{title="Community Forum" href="https://forum.weaviate.io/c/support" icon="messages-square"}
Ask questions and connect with other developers on our **Community forum**.
:::

:::card{title="Support" href="/guides/support-overview" icon="life-buoy"}
Weaviate Cloud user or customer? Find the right channel on the **Support page**.
:::
::::

## Related pages

- [Agents](./agents-index.md)
- [AI-assisted Weaviate code generation](./ai-assisted-vibe-coding-index.md)
- [APIs](./apis-index.md)
- [Authorization and authentication](./authorization-and-authentication-index.md)
- [Benchmarks](./benchmarks-index.md)
- [Best practices](./best-practices-index.md)
- [Client libraries](./clients-index.md)
- [Client Libraries / SDKs](./client-libraries-index.md)
- [Cloud](./cloud-index.md)
- [Cloud account management](./cloud-account-management-index.md)

# Agent Instructions

This portal answers questions programmatically. To receive a synthesized,
source-cited answer instead of crawling page by page, append the `?ask=`
query parameter to any page URL on this site:

    /guides/quickstart?ask=how+do+I+authenticate

Optional parameters:

- `&goal=<what-you-are-trying-to-do>` steers the answer toward your
  objective (e.g. `&goal=write+a+python+client`).
- `&version=<label>` scopes the answer to a mounted version when the
  portal publishes more than one.

The response is `text/markdown`: the answer followed by a `# Sources` list
of the portal pages it was grounded in. Status codes are the contract:

- `200` — the answer; `402` — the portal owner’s plan or answer credits are
  exhausted (surface this to your operator; do NOT retry); `429` — you are
  rate-limited; back off for the `Retry-After` seconds; `503` — the answer
  lane is temporarily unavailable; fall back to crawling the `.md` pages.

For the full corpus map read `llms.txt` at the site root; for the tool
surface (search + page fetch as MCP tools) see `/mcp`.