Skip to main content

What is Memory?

Memory is Ziet’s built-in durable storage system that persists data across actions, agent steps, and even failures. It provides:
  • Durable storage - Data persists even if agent steps fail
  • Key-value storage - Store and retrieve by unique keys
  • Semantic search - Find data by meaning, not just exact matches
  • Metadata filtering - Tag and filter entries
  • Automatic scoping - Data is isolated per run by default
  • Cross-agent sharing - Agents can hand off and share memory
Important: Memory is durable and survives failures. If an agent step fails, memory is preserved and the workflow can resume from where it left off. No database setup required - just import and use.

Core Operations

add()

Store data in memory:
Parameters:
string
required
Semantic label for easy retrieval. Always provide a descriptive key.
any
required
Any JSON-serializable data (dict, list, str, int, bool, etc.)
dict
Additional tags for filtering and organization.
Returns: entry_id (string) - Unique identifier for the stored entry Example:

get()

Retrieve the most recent value for a key:
Parameters:
string
required
The key to retrieve
Returns: The stored value, or None if key doesn’t exist Example:
Semantic or filtered search across all memories:
Parameters:
string
Natural language or keyword query. Searches across both values and keys.
dict
Filter by metadata fields
int
default:"10"
Maximum number of results to return
Returns: List of matching entries with scores
Examples:

remove()

Delete entries by entry_id or key:
Parameters:
string
Specific entry to remove
string
Remove all entries with this key
Returns: Number of deleted entries (int) Examples:

Usage Patterns

Share Data Between Actions

Store data in one action, retrieve in another:

Store Intermediate Results

Actions automatically store progress in memory:

Semantic Search for Context

Find relevant information from past actions:

Metadata for Organization

Tag and filter entries:

Clean Up Temporary Data

Remove data you don’t need anymore:

Deduplication

Avoid processing the same data twice:

Memory Durability & Agent Handoffs

Durable Across Failures

Memory persists even when agent steps fail:

Shared Across Agent Handoffs

When agents hand off to each other, memory is preserved and shared:

Best Practices

Make keys self-documentingGood
Bad
Tag entries for easy retrieval and organization
Remove data you don’t need to keep
Keep memory entries reasonably sizedGood: Store summaries or references
Bad: Store entire large objects
Write natural queries for better resultsGood: Natural language
Bad: Single keywords (use exact key instead)

Limitations

Current limitations:
  • Max entry size: 6MB per entry
  • Max entries per run: 10,000 entries
  • Retention: Data retained for 30 days after run completion
  • Search results: Limited to 100 results per query
  • Cross-run memory: Not yet available (coming soon)

Examples

Complete Flight Search Example

Next Steps

Actions

Learn how to build actions that use memory

Agents

Build agents that orchestrate memory operations

Integrations

Combine memory with integrations

API Reference

Complete API documentation