emdb-delete

Name: emdb-delete
Availability: InStock
Author: Rach

Delete vectors from EmergentDB by ID in default or specified namespaces.

Updated Feb 11, 2026

Search Tags:#api #delete #idempotent #vector #namespace #data-cleanup #emergentdb

Ready to run

npx skills add https://github.com/justrach/emergent-sdk --skill emdb-delete

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: emdb-delete
Source: https://github.com/justrach/emergent-sdk/tree/main/skills/emdb-delete
Command: npx skills add https://github.com/justrach/emergent-sdk --skill emdb-delete

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deletes vectors from EmergentDB by ID to remove outdated or erroneous entries and keep data clean.

Core Features & Use Cases

Delete a single vector by ID in the default namespace.
Delete vectors by ID within a specific namespace to target cross-namespace cleanup.
Batch delete support for multiple IDs, with idempotent results.

Quick Start

Delete the vector with a specified ID from the default namespace.

Frequently Asked Questions about emdb-delete

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

FAQPage Schema

How do I delete vectors by ID in EmergentDB?▼

You can delete EmergentDB vectors by providing their specific IDs to remove outdated or erroneous entries. This supports both single vector deletion and batch deletes across the default or specified namespaces for targeted data cleanup.

Can I delete multiple EmergentDB vectors at the same time?▼

Yes, batch deleting multiple EmergentDB vectors is supported by submitting an array of IDs. The operation returns clear results and supports idempotent deletes, meaning retrying will not cause errors if the entries are already removed.

How do I target data cleanup within a specific EmergentDB namespace?▼

To target data cleanup within a specific EmergentDB namespace, you must specify the namespace parameter during the delete operation. This allows for cross-namespace cleanup when removing vectors by ID rather than just using the default namespace.

What happens if I try to delete an invalid EmergentDB vector ID?▼

Deleting an invalid EmergentDB vector ID triggers common error handling within the operation. The system catches these invalid ID errors and returns a clear result, ensuring your data cleanup process fails safely without unexpected side effects.

Do I need an API key to delete vectors from EmergentDB?▼

Yes, you need a valid API key to delete vectors from EmergentDB. The operation explicitly handles missing API keys as a common error, returning a clear result to ensure secure and authenticated data cleanup.