Credentials. The .env file holds your provider key, so keep it out of git and out of shared logs.
Who it is forA developer or team that wants a shared wiki service that scripts and agents can call over HTTP.
The problemAdding documents and asking questions by hand does not fit into an automated workflow.
The outcomeA running wiki on port 8000 that accepts documents and questions through HTTP requests.
What you need first
- Python 3.11 or later, or uv to install it
- An API key for OpenRouter, OpenAI, Gemini or another OpenAI-compatible server, or Ollama installed for free local use
- Documents as text, Markdown, PDF, Word, PowerPoint, Excel or OpenDocument files
Steps
- Run
git clone https://github.com/crow-hq/llm-wiki-v2 && cd llm-wiki-v2. - Run
cp .env.example .env, then set OKF_LLM_PROVIDER and its key in the file. - Run
docker compose up -d --buildto start the wiki on port 8000. - Run
curl -X POST localhost:8000/ingest -H 'content-type: application/json' -d '{"text": "Acme refunds orders within 30 days of delivery.", "title": "Refund policy"}'to file a note. (inferred, check the README) - Run
curl -X POST localhost:8000/ask -H 'content-type: application/json' -d '{"question": "How long do customers have to ask for a refund?"}'to get a cited answer. (inferred, check the README)
Prompt for your agent
Clone the llm-wiki-v2 repo, start it with Docker Compose on port 8000, then POST the text in <source file> to /ingest and ask <question> through /ask. Expected output: the ingest response and an answer with cited notes. Verify that /health reports the service as running.
Caveat. With Docker the settings come from .env and the web page shows them but cannot change them.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page