Skip to main content
Three endpoints manage chunks in a vector database, the same as the SDK store(), edit(), and delete(). The collection is created automatically if it doesn’t exist.

Store (POST /v1/store)

Upsert embedded chunks (each with an embedding field) into the vector database.

Edit (POST /v1/edit)

Re-embed and replace stored chunks by ID. Pass the updated chunks with the same IDs; the server embeds them with the given provider before upserting.

Delete (POST /v1/delete)

Remove chunks by ID.
Give chunks stable IDs at chunk time so edit and delete can target them later. See Knowledge Base Maintenance.

Supported databases