> For the complete documentation index, see [llms.txt](https://docs.minded.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.minded.com/tooling/storage.md).

# Storage

The `storage` module provides utility functions for saving and retrieving document records between sessions. Records are scoped to the agent and persist across sessions.

## Import

```typescript
import { toolsLibrary } from '@minded-ai/mindedjs';

const { saveRecord, getRecords, deleteRecord } = toolsLibrary.storage;
```

## Basic Operations

**Save a record:**

```typescript
const recordId = await saveRecord(state.sessionId, {
  invoiceId: 'INV-12345',
  status: 'processed',
  amount: 1500.00,
}, 3600); // Optional: TTL in seconds
```

**Retrieve records:**

```typescript
// Simple equality
const records = await getRecords({ status: 'processed' });
```

**Delete a record:**

```typescript
await deleteRecord('record-id-123');
```

## Record Structure

* `id`: Unique identifier
* `agentId`: Automatically set to the agent ID
* `sessionId`: Session where the record was created
* `data`: Your document data
* `createdAt`: Creation timestamp
* `updatedAt`: Last update timestamp

## Notes

* Records are agent-scoped (only accessible by the same agent)
* Filters use MongoDB query syntax and apply to the `data` field (no `data.` prefix needed)
* All operations require a valid `sessionId`
* Records persist across sessions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.minded.com/tooling/storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
