Skip to main content

eno-service

A FastAPI face on eno's read endpoints — the HTTP surface other tools talk to.

eno-service is the shared, long-running face on an eno vault index. Run it once on a host and every tool that speaks HTTP — the Obsidian plugin, the eno-mcp server, sibling projects — queries the same index instead of each opening its own sqlite handle. Single-host work doesn't need it; a multi-tool or multi-agent setup does.

Install

pip install eno-service

Requires Python 3.12+. Pulls in the enowiki core (which imports as eno).

Run it

export ENO_VAULT_DIR=~/vault      # index must already exist — run `eno index` first
eno-serve                         # serves on 127.0.0.1:7891

Host and port come from $ENO_SERVICE_HOST / $ENO_SERVICE_PORT (defaults 127.0.0.1 and 7891). Point a client at it with $ENO_SERVICE_URL, e.g. export ENO_SERVICE_URL=http://localhost:7891.

Endpoints

Read (GET):

  • /health — liveness + configured vault path
  • /search — notes by title substring, body text, or tag
  • /note — frontmatter + headings + excerpt for one note
  • /neighbors — backlinks + outbound for one note
  • /orphans — notes with no inbound links
  • /stubs — short notes with no outbound links
  • /stale — notes past a recency threshold
  • /broken-links — raw broken wikilinks
  • /classify-broken-links — split into drift (real bugs) vs concepts (groundwork)
  • /frontier — pages actively reaching outward
  • /hot — session-start "what's hot" bundle
  • /hygiene — frontmatter contract audit

Write / compute (POST):

  • /index — (re)build the index
  • /tiling — body-content semantic dedup (needs the enowiki[llm] extra)
  • /garden — structural gardener report
  • /hygiene/propose, /hygiene/apply — audit proposals and applies
  • /note/create, /note/append — write notes back with provenance

The service is read-first: POST /index and the note-write endpoints are the mutating exceptions, and every write is human-initiated. Interactive API docs are served at /docs once it's running.

License

MIT — see LICENSE.

Metadata

Release files for eno-service 0.5.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for eno-service 0.5.0
File Size Uploaded Provenance Actions
eno_service-0.5.0.tar.gz 6.8 kB With provenance Details for eno_service-0.5.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for eno-service 0.5.0
File Interpreter ABI Platform Actions
eno_service-0.5.0-py3-none-any.whl Python 3 none any Details for eno_service-0.5.0-py3-none-any.whl

Total release size: 11.8 kB

Release files / eno_service-0.5.0.tar.gz

Download URL eno_service-0.5.0.tar.gz
Size 6.8 kB
Tags Source
SHA-256 checksum
How to use checksums
50cea32b8f659f8d3143eec911534c6277fbfeeb55b54d68c1a85d3a612f69b5
BLAKE2b-256 checksum
How to use checksums
06a3bc71ecc40cf28df3d1f586617d36509078f64f682a863658441f75103c83
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Release files / eno_service-0.5.0-py3-none-any.whl

Download URL eno_service-0.5.0-py3-none-any.whl
Size 5.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b54987987c156987e9dfabdd7f732ae712f5589ba2edec3bee2813687b31dc22
BLAKE2b-256 checksum
How to use checksums
402447cd9f5476f9eeb9316b3e42b85780c1be03d7815ed4d1356630d81b269b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

Security for eno-service 0.5.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for eno_service-0.5.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 28, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page