Skip to main content
Vector store file capabilities index a file into a vector store, list its files, and delete files — calling the real LiteLLM API and surfacing backend errors.
These functions call the real LiteLLM API (vector_store_file_create, vector_store_file_list, vector_store_file_delete). Backend errors now surface instead of being swallowed.

Quick Start

1

Index a file with an Agent

Use knowledge sources to let an agent index and search files automatically.
2

Direct capability call

Add an already-uploaded file to a vector store.

How It Works

vector_store_file_delete returns the real deleted flag. When the backend response has no deleted attribute, it defaults to False (previously True). Backend errors are no longer swallowed.

Configuration Options

vector_store_file_create vector_store_file_list vector_store_file_delete

Capabilities SDK Reference

Auto-generated reference for the capabilities module

Common Patterns

List then delete files:
Async indexing:

Best Practices

vector_store_file_delete returns False when the backend does not confirm deletion. Verify the return value rather than assuming success.
Real LiteLLM errors now propagate. Wrap calls in try/except to handle provider or auth failures.
For most workflows, pass files via an agent’s knowledge parameter — indexing and retrieval are handled for you.

Knowledge

Index and search documents from an agent

Capabilities Overview

All LiteLLM parity capabilities