LOGOI

Documentation

Downloads & exports

The license, plainly

Everything the estate computed itself — frequency tables, attestation lists, co-occurrence tables, etymology pointers, receipts, coverage inventories — is yours to download and reuse under CC BY 4.0. The one condition is the attribution line every file already carries: logoi.health — <receipt URL>. Corpus text is different: a passage's Greek (or Latin, Hebrew, …) keeps the license of its source edition, stated per record, and is included only where that license permits public display.

What you can download

  • GET /api/v1/export/term/{language}/{lemma}.json — the per-word record. Morphology pages behind ?include=morphology&page=N so the default file stays small.
  • GET /api/v1/export/concordance/{language}/{lemma}.json|.csv — paginated attestations (?page=&page_size=&work=).
  • GET /api/v1/export/frequency/{language}/{lemma}.json|.csv — per-work counts, normalized per 10,000 attested tokens, with a totals row in the CSV.
  • GET /api/v1/export/cooccurrence/{language}/{lemma}.json|.csv — shared-passage co-occurrence (?lemma_b=) or top companions.
  • GET /api/v1/export/passage/{stable_id}.json — the passage record, with the text where its license permits.
  • GET /api/v1/export/source/{id}.json and receipt/{id}.json — provenance and audit records.
  • GET /api/v1/export/cite/{term|passage|source}/….bib — BibTeX; the JSON exports also carry CSL-JSON and a plain citation string.
  • GET /api/v1/export/tool/{tool}.json?… — any corpus tool result as a file, through the same dispatch seam agents use.
  • /downloads — per-work bulk JSONL of open-licensed text and estate-derived columns, with a manifest.

The machine-readable map is at /api/v1/export/index.json. Every tool payload from the MCP connector and the ask instruments now carries an export_url pointing at its own download.

Why some things stay excerpt-only

The licensed reference works — Beekes, Chantraine, Frisk, BDAG, HALOT, the OED lineage, Loeb apparatus — are cited, never reprinted. In every export path their material appears only as pointers and short excerpts with the authority, locator, and entry number, so a reader who holds the source can find the entry. This is enforced in the export layer itself, not by policy alone: citation-only prose is clamped to excerpt length even if a stored row were ever wider. Open lexica (LSJ under its open release) ship whole, with their own license stamped.

How to cite what you download

Each JSON export carries a cite block (BibTeX, CSL-JSON, and a plain string). For a passage, the citation names the stored edition — editor, publisher, year — with the Logoi receipt URL in the note. See the citation policy for the receipts law.