Semantica
Builds a knowledge graph from your documents without calling an LLM, then answers agents through graph traversal, causal chains, and decision records that keep their provenance.
What it provides
Connect an existing HTTPS deployment, with a scoped token where the service requires one. Heavy jobs stay on that service instead of using bot memory.
Connection requirements
Install `semantica[explorer]` and run `python -m semantica.server` outside the bot, then publish port 8000 through an HTTPS reverse proxy. Current releases protect the Explorer API with SEMANTICA_API_KEY: set that key on the service host, leave SEMANTICA_ALLOW_ANONYMOUS unset, keep x-api-key selected, and paste the same key below. Protected routes return 503 if the server key is missing, or 401 if the X-API-Key header is missing or incorrect. SEMANTICA_SECRET_KEY does not add API authentication. Keep port 8000 itself unreachable from the internet by using a private network or firewall. Older releases without Explorer authentication still require authentication at the proxy. The Explorer API routes are mounted only when the explorer imports succeed: if they fail, those routes return 404, so confirm with `get /api/graph/stats`. Keep extraction, embeddings, and persistent graph and vector stores on the external host.
- Protocol
- REST / OpenAPI
- Endpoint
https://semantica.example.com- Authentication
- x-api-key
post /api/enrich/extract {"text":"Apple CEO Tim Cook announced record earnings."}get /api/graph/node/acme_corp/neighbors?depth=2get /api/graph/statsWhere to add it
Open Dashboard Tools, select a running OpenClaw or Hermes instance, then use the card’s Install or Connect action. External services may require an HTTPS endpoint and credentials; the dashboard shows those fields before anything is saved.