deepwiki.com APIdeepwiki.com ↗
Access DeepWiki's indexed GitHub repository documentation: search repos, fetch markdown wiki pages, table of contents, and source file references via 7 endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/4ff5812b-da87-4646-b5f3-360abc785560/get_homepage_featured_repos' \ -H 'X-API-Key: $PARSE_API_KEY'
Retrieve the list of featured/popular repositories displayed on the DeepWiki landing page. Returns all indexed repositories sorted by popularity.
No input parameters required.
{
"type": "object",
"fields": {
"repositories": "array of repository objects, each with id, repo_name, last_modified, description (nullable), stargazers_count (nullable integer), language (nullable), topics (nullable array of strings)"
},
"sample": {
"data": {
"repositories": [
{
"id": "v1.9.9.5/PUBLIC/microsoft/vscode/161a11c5",
"topics": [
"editor",
"electron",
"visual-studio-code"
],
"language": "TypeScript",
"repo_name": "microsoft/vscode",
"description": "Visual Studio Code",
"last_modified": "2026-04-29T01:38:20.916458+00:00",
"stargazers_count": 183870
}
]
},
"status": "success"
}
}About the deepwiki.com API
The DeepWiki API exposes 7 endpoints for retrieving AI-generated documentation wikis for GitHub repositories indexed on DeepWiki.com. You can search repositories by keyword or owner/repo pattern using search_repositories, pull full markdown wiki content page-by-page with get_repo_wiki_page, or dump an entire repository's documentation at once via get_repo_wiki_all_pages. Each wiki page response includes the markdown content and an array of source file paths that the documentation references.
Discovery and Search
get_homepage_featured_repos returns the full list of repositories DeepWiki surfaces on its landing page, each with id, repo_name, last_modified, description, and stargazers_count. search_repositories accepts a query string in plain keyword or owner/repo format and returns the same repository object shape. get_user_or_org_profile takes a username and returns name, bio, type ('User' or 'Organization'), avatar URL, and an indexed_repositories array of every repo that user or org has documented on DeepWiki.
Wiki Content Retrieval
Before fetching content, call check_repo_wiki_exists with owner and repo parameters to confirm a wiki is available — it returns a single exists boolean alongside the repo string. get_repo_wiki_overview then returns the repository metadata (including language and topics fields not present in search results), a markdown overview string, and a table_of_contents array of objects containing slug, title, and id. These slugs are the keys to individual pages.
Page-Level and Bulk Content
get_repo_wiki_page takes owner, repo, and a slug (e.g. '1.2-build-system-and-cicd') and returns the full content as a markdown string plus relevant_source_files — an array of file paths within the repository that the wiki page draws from. For cases where you need all documentation at once, get_repo_wiki_all_pages returns a pages array where each entry carries slug, title, content, and relevant_source_files, covering the entire indexed wiki in a single call.
- Building a code documentation search tool that indexes wiki content across multiple GitHub repositories using
get_repo_wiki_all_pages - Generating repository summaries by combining
get_repo_wiki_overviewmetadata fields likelanguage,topics, and the markdownoverview - Checking whether a repo has documentation before offering a 'docs' link in a developer dashboard, using
check_repo_wiki_exists - Aggregating all repositories for a GitHub organization using
get_user_or_org_profileto listindexed_repositories - Feeding LLM context windows with structured markdown documentation and
relevant_source_filesfromget_repo_wiki_page - Surfacing trending open-source projects by polling
get_homepage_featured_reposand sorting bystargazers_count - Mapping which source files are most referenced across a codebase by collecting
relevant_source_filesfrom every page viaget_repo_wiki_all_pages
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does DeepWiki have an official developer API?+
What does `get_repo_wiki_overview` return that search endpoints don't?+
get_repo_wiki_overview returns a metadata object that includes language and topics fields, which are not present in repository objects returned by search_repositories or get_homepage_featured_repos. It also returns the full markdown overview text and the table_of_contents array with slug, title, and id entries needed to fetch individual pages.Can I retrieve wikis for repositories not yet indexed on DeepWiki?+
check_repo_wiki_exists will return exists: false for unindexed repos. The API covers search, profile lookups, and content retrieval for the existing DeepWiki index. You can fork this API on Parse and revise it to add an endpoint that triggers indexing or monitors indexing status if DeepWiki exposes that capability.Is there a way to filter `search_repositories` results by language, topic, or star count?+
search_repositories endpoint accepts only a query string and returns an unfiltered array of matching repository objects. Client-side filtering on stargazers_count or description is possible with the returned data, but server-side filtering parameters are not currently supported. You can fork this API on Parse and revise it to add filter parameters if the underlying data supports it.How fresh is the wiki content returned by these endpoints?+
last_modified field indicating when DeepWiki last updated that repository's documentation. The API reflects the current state of DeepWiki's index at the time of the request — it does not expose historical versions or changelogs for wiki pages.