Leadtype
Leadtype
Leadtype is a docs pipeline. You write MDX in one place. It produces the generated artifacts your docs need: markdown mirrors, llms.txt, root llms-full.txt, search JSON, Agent Readability metadata, and package-bundled AGENTS.md output.
It is not a docs website framework. Bring your own UI — Next.js, TanStack Start, Astro, anything — and let leadtype handle conversion, validation, search, and the agent-facing outputs that website frameworks don't ship.
Choose your path
Pick the job that matches what you are building. Each path starts with the minimum setup, then links to the lower-level API reference only when you need it.
Connect a docs site
Clone source docs from a package repo, generate hosted artifacts, and wire the output into your app.
Add search
Generate a static BM25 index, query it at runtime, and optionally stream source-grounded answers.
Ship docs in your package
Publish AGENTS.md plus relative markdown files inside an npm tarball.
What you get
Author MDX with familiar components — Callout, Tabs, Steps, Mermaid, TypeTable, and others. Add group: in frontmatter to place pages in the navigation tree.
For a website: converts MDX to markdown, builds llms.txt plus root llms-full.txt, generates a search index, writes Agent Readability discovery files, and resolves navigation. With --bundle: emits AGENTS.md plus per-topic .md files with relative links that still work after npm install.
Humans get HTML from your app. HTTP agents get markdown via content negotiation or /llms.txt. Package consumers can point their root AGENTS.md or README at node_modules/<your-pkg>/AGENTS.md for version-matched offline docs.
Next
- New here? Read the Quickstart — five minutes to generated output.
- Want the mental model first? Read How it works for the pipeline diagram and the names of every artifact it produces.
- Comparing tools? See Methodology for how leadtype differs from Fumadocs, Starlight, and Mintlify.