Repo to Markdown
In the product: Repo to Markdown tool and the /repo documentation views. API: GET /v2/repos/{repo_id}/blueprint for repo-level Markdown; GET /v2/files/{repo_id}/{file_id} for file-level docs.
Convert entire repositories into a structure-aware, token-optimized map. Perfect for RAG, documentation, prompt engineering, and agent context windows.
How to use it in the web app
Repo to Markdown tool
Open /tools/repo-to-md, paste a repository URL, and convert. Output is LLM-ready Markdown you can copy into ChatGPT, Claude, Cursor, or your agent stack.
Repo documentation pages
On /repo, browse the indexed library, open a repository blueprint (README plus dependency overview), then drill into per-file Markdown summaries.
Depth by plan
Richer field presets (summary, full) unlock on higher tiers. See Credits and tiers.
What the map contains
- Repo-level documentation Markdown and README text
- Top dependencies and (plan-dependent) conventions / symbols
- Per-file documentation summaries
If documentation is still processing, file get indicates processing and is not charged.
Same capability via API
- Prefer
GET /v2/repos/{repo_id}/blueprint(canonical; do not use deprecated/readme). - List files:
GET /v2/files/{repo_id}. - File Markdown:
GET /v2/files/{repo_id}/{file_id}?fields=full(orsummary/basic).
Guides: V2 Blueprint, V2 Files.