Indykite capture delete node properties

IndyKite Capture - delete node properties

This skill builds the request body for the Capture API's batch node-property delete endpoint - removing named properties from nodes in the IndyKite Knowledge Graph (IKG) while keeping the nodes themselves:

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

Each entry names one node by (type, external_id) and lists the property_types to strip. 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 specific properties from a node - PII minimization, dropping deprecated fields, correcting a wrong ingest - while keeping the node;
• strip the same property set from many nodes in one call.

Do not activate this skill to:

• delete the whole node - use indykite-capture-delete-nodes;
• remove only a property's metadata (value survives) - use indykite-capture-delete-node-property-metadata;
• remove relationship properties - use indykite-capture-delete-relationship-properties;
• overwrite a property with a new value - just re-upsert it with indykite-capture-upsert-nodes;
• delete through a CIQ policy + Knowledge Query - 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) of each node and the exact property names to remove.

Steps

1. List the nodes and the properties to strip

Field	Required	Constraints	Meaning
external_id	yes	1-256 chars	The node's caller-owned identifier.
type	yes	2-64 chars	The node's type.
property_types	yes	1-250 names	The property names to delete from this node.
location	no	2-32 chars	Composite IKG only: the node's logical location. Omit on a regular IKG.

2. Assemble the request body

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

{
  "nodes": [
    {
      "external_id": "millicent",
      "type": "Person",
      "property_types": ["email", "given_name"]
    }
  ]
}

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 property 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": [ … ] } body exists, each entry naming a node and its property_types to remove.
• If sent, the listed properties are gone from those nodes; the nodes, their other properties, and their relationships are untouched.

Files in this skill

• references/capture-reference.md - field reference, batch limits, and error semantics.
• assets/delete-node-properties.json - ready request body stripping two properties from a Person.
• scripts/capture.sh - Bash helper that POSTs a body file to /capture/v1/nodes/properties/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