Indykite Capture Delete Nodes

IndyKite Capture - delete nodes

This skill builds the request body for the Capture API's batch node delete endpoint - removing whole nodes from the IndyKite Knowledge Graph (IKG):

POST <API_URL>/capture/v1/nodes/delete

Each entry references one node by (type, external_id) - the same pair that identified it at upsert. The JSON file is the deliverable, ready to be POSTed by any application.

The MCP server does not currently expose Capture endpoints; the JSON bodies this skill produces are for direct REST use and remain valid if Capture tools are added later.

When to use

Activate this skill when the user wants to:

• remove entities from the IKG - cleanup of test data, offboarding a record, retiring a device;
• undo a batch ingested with indykite-capture-upsert-nodes.

Do not activate this skill to:

• remove individual properties (node survives) - use indykite-capture-delete-node-properties;
• remove property metadata (property survives) - use indykite-capture-delete-node-property-metadata;
• remove relationships - use indykite-capture-delete-relationships;
• delete through a CIQ policy + Knowledge Query (parameterized, authorization-gated deletes) - use indykite-ciq-delete.

Prerequisites

• An IndyKite project with an AppAgent whose credentials are configured for the calling application (Credentials guide).
• The (type, external_id) pairs of the nodes to remove.

Steps

1. List the nodes to delete

2. Assemble the request body

One JSON object: { "nodes": [ … ] }, 1-250 entries per request. A ready example: assets/delete-nodes.json.

{
  "nodes": [
    { "external_id": "kitt", "type": "Car" },
    { "external_id": "ryan", "type": "Person" }
  ]
}

This file is the deliverable - any HTTP-capable application can send it.

3. Send it (optional)

The endpoint authenticates the calling application (its AppAgent credentials). Which credential goes in which request header is covered by the Credentials guide.

A runnable shell helper builds the authenticated request: scripts/capture.sh — run with --print to preview the curl (host-pinned; token redacted). Deletion is destructive: preview with --print, and confirm the target list, before sending.

4. Read the results

A 200 returns one result per node, in order: { "results": [ { "id": "gid:…" } ] }. Field shapes and error semantics: references/capture-reference.md.

Outcome

• A valid { "nodes": [ … ] } delete body exists, each entry a (type, external_id) reference.
• If sent, the nodes are gone from the IKG and no longer appear in CIQ query results or KBAC decisions.

Files in this skill

• references/capture-reference.md - field reference, composite-IKG location behavior, batch limits, and error semantics.
• assets/delete-nodes.json - ready request body removing a Car and a Person.
• scripts/capture.sh - Bash helper that POSTs a body file to /capture/v1/nodes/delete (host-pinned; --print to preview).

Agent-specific notes

This skill uses generic markdown instructions and works across all agents listed in the README. The agent needs to be able to write a JSON file; sending it additionally requires HTTP access (curl or any HTTP client).

References

• Capture API reference (OpenAPI)
• Data Residency guide - location-aware deletes on composite IKGs
• Credentials guide