emdb-insert

Insert vectors with metadata into EmergentDB via official SDKs.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/justrach/emergent-sdk --skill emdb-insert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: emdb-insert
Source: https://github.com/justrach/emergent-sdk/tree/main/skills/emdb-insert
Command: npx skills add https://github.com/justrach/emergent-sdk --skill emdb-insert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Insert vectors into EmergentDB using the official SDKs to store embeddings, index documents, or batch upload vectors, enabling scalable similarity search and retrieval.

Core Features & Use Cases

  • Single insert of a vector with optional metadata (title, content, etc.)
  • Batch insert for up to 1000 vectors per call, with batchInsert / batch_insert
  • Upsert behavior: re-inserting an existing ID replaces it in the same namespace
  • Namespace support with a default namespace and automatic creation
  • Dimension checks: embeddings must match index dimension (default 1536)
  • Metadata fields supported: title, content, source_url, tags

Quick Start

Choose your preferred SDK (TypeScript or Python) and perform a single vector insert or a batch upload to EmergentDB.

Frequently Asked Questions about emdb-insert

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I insert embeddings into EmergentDB using the official SDK?

Insert embeddings into EmergentDB using official TypeScript or Python SDKs by providing vectors, optional metadata like title or source_url, and a valid API key. The SDK handles dimension checks and namespace routing automatically.

How do I batch upload vectors to EmergentDB and what is the maximum batch size?

Batch upload vectors to EmergentDB using the batchInsert or batch_insert SDK methods. Each batch insert call supports a maximum of 1000 vectors and enforces strict dimension checks against the index before persisting the embeddings.

What happens when I upsert a vector with an existing ID in EmergentDB?

Upserting a vector with an existing ID in EmergentDB replaces the previous vector and its metadata within the same namespace. Re-inserting an existing ID functions as an update rather than generating a duplicate record.

Does EmergentDB support custom namespaces for vector insertion?

Yes, EmergentDB supports optional namespaces during vector insertion with a default namespace fallback. If a specified namespace does not exist, the SDK automatically creates it before persisting the embeddings and metadata.

What metadata fields can I attach when storing vectors in EmergentDB?

When storing vectors in EmergentDB, you can attach optional metadata fields including title, content, source_url, and tags. These metadata fields are persisted alongside the embeddings to support filtered similarity search.

Why does my vector insertion fail with a dimension mismatch error in EmergentDB?

Vector insertion fails when embeddings do not match the index dimension, which defaults to 1536. Ensure your generated embeddings align with the configured dimension constraints before attempting to batch insert or upsert.