Ingestion and exploration

Ingest raw text

ingestGraphText() and ingestGraphDocuments() use the same TextDocument and chunking contracts as Core vector ingestion. They chunk source text, extract facts, embed chunks and entities, and atomically replace each source document in the managed graph.

const result = await ingestGraphText({
  graph,
  document: {
    id: 'incident-42',
    text,
    metadata: { tenant: 'acme' },
  },
  extractionModel,
  embeddingModel,
  chunking: {
    strategy: 'recursive',
    maxSize: 1_000,
    overlap: 100,
    separators: ['\n\n', '\n', ' '],
  },
  conflict: 'error',
  orphanEntities: 'delete',
})

console.log(result.write)

The result contains exact change counts and vectorDocuments, grouped by source document ID. Reuse those embeddings in a vector store without another model request:

await vectorStore.upsert({ documents: result.vectorDocuments })

The graph and vector writes are separate transactions. Persist application-level ingestion status when both stores must be reconciled. Use prepareGraphDocuments() to prepare both outputs without performing either write.

Explore a graph

Any adapter implementing GraphExplorer supports a bounded overview and follow-up expansion:

const overview = await graph.explore({
  mode: 'overview',
  nodeTypes: ['Product'],
  maxNodes: 100,
  maxRelationships: 200,
})

const neighborhood = await graph.explore({
  mode: 'expand',
  nodeIds: [overview.nodes[0]!.id],
  direction: 'both',
  maxDepth: 1,
})

Explorer IDs are opaque and provider-specific. Use them only to expand the current view; use schema identity properties for application logic. The shared contract caps requests at 500 nodes, 1,000 relationships, depth 4, and 20 expansion roots. Adapter responses report truncation and omit stored embeddings and reserved Anvia properties.

Register the explorer in Studio for an interactive view.