Vector search, built in

Curiosity includes a vector database. Embeddings are generated, stored, and queried in the same system as your graph: no separate infrastructure to build or maintain.

From data to semantic search

Mark a field as vector-indexed and Curiosity handles the rest: embedding, indexing, and retrieval all run inside the same platform.

Embed

Text fields are encoded into vectors automatically at ingestion, using your choice of embedding model.

Store

Vectors live in an in-memory index inside Curiosity. No external vector database needed.

Query

Search by meaning, find similar items, or ground LLM responses — all through the same API you already use.

Questions for developers

Common questions from developers building on Curiosity.

Which model does Curiosity run?
What can I build on Curiosity?
How does the knowledge graph work?
Can I run models on my own system?
Can I connect custom data sources?
How do I build agents?
Can I extend the platform with custom logic?
Can I run Curiosity on my own infrastructure?
How are permissions enforced in what I build?
How do search and embeddings work together?
How do I get started?

Connected knowlege for AI systems

Connected knowlege for AI systems