IndyKite Data Schema - read the IKG's observed schema

The IndyKite Knowledge Graph (IKG) has no up-front schema definition step: the schema emerges from the data ingested through the Capture API or ContX IQ upserts. The platform tracks that emergent schema - which node types exist, which properties they carry with which value types, and how the types are connected - and exposes it through the Data Schema API as a JSON Graph Format (JGF) v2 document.

It is a schema-level view only: type names, property names, observed value types, and occurrence counts. It never returns the data itself, so it is safe to hand to tools and agents that should know the graph's vocabulary without seeing its contents.

When to use

Activate this skill when the user wants to:

• discover the exact spelling of node types, relationship types, and property names before authoring Cypher - a CIQ policy or Knowledge Query (indykite-ciq-read and siblings) or a KBAC policy (indykite-authzen-kbac-policies) references them literally, and a policy written against givenName matches nothing when the data was ingested as given_name;
• verify an ingest - after a Capture batch, one GET confirms the expected types and properties landed and the counts sanity-check the volume (a "Perosn" typo shows up immediately as a surprise node type);
• detect schema drift or data-quality issues - a property reporting string: 4980, integer: 20 means an upstream source started sending the wrong type;
• get a meta-model overview of the project's graph ("what does our IKG look like?") for onboarding, visualization, or impact analysis before a cleanup.

Do not activate this skill when the user: