Skip navigation
Get augmented, not replaced

The lokaliQ API

lokailiQ aims to give you the tools you need to succeed - safely, securely , with human oversight.

Your data. Your rules. Your automation.

Built API first

The same engine that powers the web interface is available as a clean, documented REST API —
ready for scripts, pipelines, integrations, and anything else you can think of

Query your knowledgebase

Ask questions, get answers with sources. The same RAG pipeline — retrieval, reranking, LLM synthesis — available as a single POST request. Stream responses in real time or collect the full answer. Conversation memory carries across turns, just like in the chat.

Ingest From Anywhere

Upload documents, trigger ingestion, monitor progress. Feed your knowledge base from CI/CD pipelines, scheduled jobs, or custom workflows. PDF, DOCX, markdown, audio — the API accepts what the interface accepts.

Manage Projects Programmatically

Create projects, configure domains, check statistics, update settings. Everything that makes LokalIQ a multi-tenant knowledge platform is accessible through standard CRUD endpoints.

What's Under the Hood

The API exposes the full LokalIQ stack:

  • vector search (ChromaDB)
  • semantic reranking (cross-encoder)
  • entity graphs (NetworkX),
  • conversation memory
  • web search (SearXNG)
  • Norwegian law integration (Lovdata)
  • audio transcription
  • and multi-provider LLM support

— all scoped per project, per domain.

lokaliq-mermaid-description

Technology is no longer the bottleneck; the real frontier is trust in how data is handled. lokaliQ dissolves that barrier.

Bjørn Marius Narjord, CEO Optimalisert AS
Federate Knowledge Across Instances

The Federation API lets separate LokalIQ instances share knowledge. Publish a domain, issue an API key, and other instances can query your data — or you can query theirs. Each instance stays sovereign. No central authority required.

Security Without Ceremony

Scoped API keys control what each integration can do. A data pipeline gets query and ingest access. A dashboard gets read-only project access. Keys are hashed in configuration — no database, no token servers, no OAuth dance. The web interface continues to use its existing session-based login.