You felt a handful. The library holds hundreds.

• Search — Search the Interface Lineage corpus by keyword. Returns matching dossiers — dissected interfaces, design principles, and people — ranked by relevance. Use this to locate a design before fetching it. Optionally narrow by semantic_type.
• Fetch — Fetch one dossier by its id/slug (as returned by search) and return the full article as Markdown, followed by its lineage edges. This is the grounded source text — read it before making claims about the design.
• Get Lineage — Return the explicit, hand-authored lineage edges for a dossier — the typed influence graph (came_after, came_before, inspired_by, influenced, contrasts_with, extends, embodies, …). This is the corpus's core value and cannot be reconstructed from a plain read. Use direction to get only inbound or outbound edges.
• Find Related — Find designs that are semantically SIMILAR to a dossier even when no explicit lineage edge connects them — the "you should also look at this" move. Ranked by visual/semantic similarity; already-linked designs are excluded (use get_lineage for those). Pair this with get_lineage to see both the acknowledged influences and the hidden cousins.
• Get Stills — Return the actual screenshots and stills from a dossier as images, so the interface under discussion can be seen rather than only described. Call it alongside `fetch` whenever the design is visual — a gesture, a layout, a piece of chrome. Images cost far more context than text, so ask for the two or three that carry the argument, not the whole set.
• List Catalog — Sample the corpus catalog for a semantic_type — a page of interfaces, principles, people, or patterns to orient before searching. Deliberately a sample, not an exhaustive dump; use `search` to find specific designs.

Schemas and invoke metadata: Directory API