Monolex tools / Ingest

Bring sources into memory.

Web pages, API contracts, encyclopedic context, live feeds, and local files enter through different doors. They leave as readable Markdown in one searchable memory.

WEBAPIWIKIFEEDFILE

MARKDOWN

MONOMENTO
MEMORY

01 / Choose the door

Start with the source.

The tools share an outcome, not an interface. Choose the source you already have. Each tool converts it, keeps the useful structure, and can hand the result to Monomento for search and section-level reading.

WEB → MONOFETCH

monofetch fetch https://example.com/llms-full.txt

Fetch a page or documentation surface, convert it to Markdown, and index it. Crawl llms.txt or a sitemap when the source is a collection.

Why monofetch ↓

02 / One motion

Convert once. Read by meaning.

The intake tools stop at clean, indexable documents. Monomento owns retrieval across those documents. That separation keeps acquisition honest and memory reusable.

01 / ACQUIRE

Meet the source where it lives.

URL, specification, article title, feed, or local path.

02 / NORMALIZE

Preserve structure as Markdown.

Headings, sections, tables, and readable text become a durable document.

03 / REMEMBER

Search the shared index.

Use Monomento to find the passage, inspect its shape, and read the relevant section.

03 / Five doors

Use the narrowest tool.

A dedicated tool knows more about its source than a universal importer. The examples below are entry points, not a duplicated command reference.

WEB / MONOFETCH

Pages and documentation sites

Use for HTML or Markdown URLs. It also recognizes documentation collections exposed through llms.txt, llms-full.txt, and sitemaps. Its search stays scoped to fetched web pages when you want a clean web-only result.

FIRST MOTIONmonofetch fetch https://example.com/guide

API / MONOAPI

OpenAPI contracts

Use a remote URL or a local specification. MonoAPI turns the contract into navigable Markdown and indexes it without pretending an API schema is ordinary prose.

FIRST MOTIONmonoapi fetch ./openapi.yaml

WIKI / MONOWIKI

Encyclopedic context

Fetch a Wikipedia article by title, choose a language when needed, or search Wikipedia before importing. Use it for shared background, not as a substitute for a primary source.

FIRST MOTIONmonowiki fetch "Terminal emulator"

FEED / MONORSS

RSS and Atom streams

Preview a feed, then bring its entries into memory. Use it when the changing sequence matters — releases, journals, and project updates — rather than treating every entry as an unrelated page.

FIRST MOTIONmonorss peek https://example.com/feed.xml

FILE / MONODOC

Files already in your hands

Convert or index local documents, data, media, notebooks, and archives. Use Monodoc for the local artifact; keep URLs with Monofetch and feeds with MonoRSS so the source contract stays legible.

FIRST MOTIONmonodoc index ~/Documents/research/report.pdf

04 / Hand off cleanly

Know when this family stops.

Ingest is deliberately narrow. Dynamic browsing and cross-source retrieval belong to adjacent tools with their own contracts.

The page needs a browser.

Monofetch reads server-delivered content. For JavaScript-heavy pages, interactive states, or browser inspection, hand the URL to MonoSurf.

Open MonoSurf →

The source is already indexed.

Stop fetching. Search all remembered material, inspect the document outline, and read the section you need with Monomento.

Open Monomento guide →