docsloth.dev

Build on the open engine

Contracts are generated, packages are versioned, and the renderer is permissively licensed. Start with the quickstart, then take the API, the component SDK or the MCP interface. The long-form manuals stay in the repositories; this site links them instead of copying them.

Guides by task

• Getting started and product instructions — the developer hub: install, onboard, generate, publish and maintain.
• Self-hosting — the compose profile and local CLI mode, with what a static CDN cannot do; on docsloth.org.
• BYOK credentials — deployment and per-tenant model keys, including the probe path.
• Agent guides — AGENTS.md/SKILL.md authoring, MCP tools and machine-readable publications.
• Registry integration — package, sign and install from the open, federated registry.
• Generated reference — how entries are versioned and evidenced.
• Playground — render DocBlocks with the published renderer.
• Benchmarks — the evaluation method for managed intelligence.

Repository manuals

• Core repository README — Prerequisites, install commands and the tested build/test flows.
• API reference document — The written reference behind the generated operation list.
• BYOK model credentials — Deployment BYOK and hosted per-tenant credentials, with the exact API paths.
• Agent authoring — AGENTS.md/SKILL.md generation and the consent rules for agents.
• OpenAPI and MCP bridge — How the OpenAPI documents become agent tools.
• Component trust classes — What pure, interactive and connected components may do.
• Component package format — The X1 manifest, digest and capability contract.
• Market flow — Publish, discover, verify, install and render, with the evidence commands.
• Self-hostable registry build — Building the static registry tree (index.json, llms.txt, sitemap).

Agents can fetch /llms.txt for a machine index of this host.

Actions