Indykite Capture Delete Node Property Metadata

IndyKite Capture - delete node property metadata

This skill builds the request body for the Capture API's batch property-metadata delete endpoint - removing metadata fields (provenance such as source, assurance_level, verified_time, custom_metadata) from a node property in the IndyKite Knowledge Graph (IKG), while keeping the property and its value:

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

Each entry names one node by (type, external_id), one property_type on it, and the metadata_fields 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:

• strip provenance metadata from a property - e.g. drop a stale verified_time or an obsolete source - without touching the property value;
• clean metadata that feeds trust scoring so a factor no longer contributes.

Do not activate this skill to:

• delete the property itself (value and all) - use indykite-capture-delete-node-properties;
• delete the whole node - use indykite-capture-delete-nodes;
• set or update metadata - re-upsert the property with a metadata object via indykite-capture-upsert-nodes.

Prerequisites

• An IndyKite project with an AppAgent whose credentials are configured for the calling application (Credentials guide).
• For each target: the node's (type, external_id), the property name, and the metadata field names to remove.

Steps

1. List the targets

One entry addresses one property; to clean several properties on the same node, add one entry per property.

2. Assemble the request body

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

{
  "nodes": [
    {
      "external_id": "millicent",
      "type": "Person",
      "property_type": "name",
      "metadata_fields": ["assurance_level", "source"]
    }
  ]
}

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).

4. Read the results

A 200 returns one result per entry, 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, one property_type, and the metadata_fields to remove.
• If sent, those metadata fields are gone from the property; the property value, the node, and everything else are untouched.

Files in this skill

• references/capture-reference.md - field reference, the metadata field names, batch limits, and error semantics.
• assets/delete-property-metadata.json - ready request body stripping assurance_level and source from a property.
• scripts/capture.sh - Bash helper that POSTs a body file to /capture/v1/nodes/properties/metadata/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)
• Trust Score guide - how property metadata feeds scoring
• Credentials guide