Create Stores

Stores are AI-powered search indexes that organize your files for semantic search. Choose the right configuration for your use case, from temporary development environments to public knowledge bases.

Basic Creation

Create a new Store with default settings:

When you create a Store, you get a Store object with a unique ID (UUID). You can use either the ID or the name you provide as Store identifiers in all operations.

For complete details on the Store object structure, see Data Models.

Configuration Options

Name

Names and IDs are interchangeable identifiers for all operations.

Names must be unique within your organization and can be updated at any time.

Expiration Policies

Set automatic cleanup policies to manage Store lifecycle based on activity:

The last_active_at anchor resets the expiration timer whenever you add files, delete files, or perform searches. Stores never expire unless explicitly configured.

Public Access

Control read access to your Store:

Private (default): Only your organization can access. You pay all costs.

Public: Anyone with an API key can search. They pay for their own searches.

Store Configuration

Configure how files are processed and how metadata is used for search context:

Contextualization: Control whether metadata is included when embedding chunks to improve search relevance. When enabled, metadata fields are added to the chunk text before embedding, making searches more contextually aware.

false (default): Chunks are embedded without metadata
true: All metadata fields are included (flattened)
Array of field names: Only specified fields are included (supports nested fields with dot notation)

Example with Contextualization:

store = client.stores.create(
    name="docs-store",
    config={
        "contextualization": {
            "with_metadata": ["title", "author.name", "category"]
        }
    }
)

This configuration will include the title, author.name, and category metadata fields when creating embeddings for chunks, making searches more accurate when these attributes are relevant to the query.

Configuration Guide

Use Case	Name Pattern	Expiration	Public	Purpose
Development	`dev-{feature}`	7 days	No	Temporary testing
Production Docs	`docs-v{version}`	Never	Yes	Public documentation
Customer Data	`customer-{id}`	Never	No	Private customer content
Demo/POC	`demo-{client}`	30 days	No	Time-limited demos

Combined Configuration

Use multiple configuration options together for specific use cases:

Create Stores

On this page