Discover/DeepWiki API
live

DeepWiki 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.

Endpoint health
verified 5d ago
get_homepage_featured_repos
get_user_or_org_profile
get_repo_wiki_overview
check_repo_wiki_exists
get_repo_wiki_page
7/7 passing latest checkself-healing
Endpoints
7
Updated
22d ago

What is the DeepWiki 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.

Try it

No input parameters required.

api.parse.bot/scraper/4ff5812b-da87-4646-b5f3-360abc785560/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/4ff5812b-da87-4646-b5f3-360abc785560/get_homepage_featured_repos' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace deepwiki-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

from parse_apis.deepwiki_api import DeepWiki, Repository, WikiPage, WikiOverview, WikiStatus, Profile, TocEntry

client = DeepWiki()

# Search for repositories by keyword
for repo in client.repositories.search(query="fastapi"):
    print(repo.repo_name, repo.stargazers_count, repo.language)

# Get a user/org profile with their indexed repos
profile = client.profiles.get(username="microsoft")
print(profile.name, profile.type, profile.bio)

for indexed_repo in profile.indexed_repositories:
    print(indexed_repo.repo_name, indexed_repo.language)

# Get wiki overview with table of contents
overview = client.wikioverviews.get(owner="microsoft", repo="vscode")
print(overview.repo, overview.overview[:100])

for entry in overview.table_of_contents:
    print(entry.slug, entry.title)

# Fetch a specific wiki page by slug
page = client.wikipages.get(owner="microsoft", repo="vscode", slug="1.1-repository-structure-and-build-system")
print(page.slug, page.content[:100])
print(page.relevant_source_files)

# Check if a wiki exists for a repo
status = client.wikistatuses.check(owner="facebook", repo="react")
print(status.repo, status.exists)
All endpoints · 7 totalmissing one? ·

Retrieve the list of featured/popular repositories displayed on the DeepWiki landing page. Returns all indexed repositories sorted by popularity. No parameters required.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "repositories": "array of repository objects with id, repo_name, last_modified, description, stargazers_count, language, topics"
  },
  "sample": {
    "data": {
      "repositories": [
        {
          "id": "v1.9.9.5/PUBLIC/microsoft/vscode/6a4e80f4::main",
          "topics": [
            "editor",
            "electron",
            "visual-studio-code"
          ],
          "language": "TypeScript",
          "repo_name": "microsoft/vscode",
          "description": "Visual Studio Code",
          "last_modified": "2026-06-06T08:54:36.137997+00:00",
          "stargazers_count": 183870
        }
      ]
    },
    "status": "success"
  }
}

About the DeepWiki API

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.

Reliability & maintenanceVerified

The DeepWiki API is a managed, monitored endpoint for deepwiki.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when deepwiki.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official deepwiki.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
5d ago
Latest check
7/7 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • 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_overview metadata fields like language, topics, and the markdown overview
  • 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_profile to list indexed_repositories
  • Feeding LLM context windows with structured markdown documentation and relevant_source_files from get_repo_wiki_page
  • Surfacing trending open-source projects by polling get_homepage_featured_repos and sorting by stargazers_count
  • Mapping which source files are most referenced across a codebase by collecting relevant_source_files from every page via get_repo_wiki_all_pages
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does DeepWiki have an official developer API?+
DeepWiki does not currently publish an official public developer API or API documentation. This Parse API provides structured access to the documentation data available on deepwiki.com.
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?+
No. All endpoints only return data for repositories already 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?+
The 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?+
Each repository object includes a 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.
Page content last updated . Spec covers 7 endpoints from deepwiki.com.
Related APIs in Developer ToolsSee all →
github.com API
Look up GitHub repositories and users: search repositories, fetch repository metadata, releases, issues and issue threads, browse repository files/trees, and retrieve user profiles and starred repositories.
wikia.org API
Search and retrieve detailed information about characters, episodes, lore, and other content from Fandom wikis across thousands of fan communities. Browse wiki categories, look up specific pages, and access structured data about your favorite franchises all in one place.
gitee.com API
Search and explore Gitee repositories by category, view repository metadata and contents, and discover projects from specific users. Access commit history, file structures, and repository details all in one place.
gamepedia.com API
Search gaming wikis across Fandom to find guides, maps, strategies, and game information, then retrieve detailed page content in multiple formats along with images and metadata. Discover trending articles, browse categories, and navigate game-specific knowledge bases to get the gaming data you need.
wikia.com API
Extract structured data from Fandom (formerly Wikia) gaming wikis. Search pages, retrieve full page content, list category members, and convert wiki pages into organized guides with infoboxes, section breakdowns, and clean text.
docs.opensearch.org API
Search OpenSearch documentation across multiple versions, retrieve specific page content, discover breaking changes, and navigate the docs structure all from a single interface. Instantly find answers by searching the docs or get a complete overview of available versions and site navigation.
Docs.copia.io API
Search and browse the complete Copia Automation documentation, discover available pages, and retrieve full text content from any page on docs.copia.io. Quickly find answers by searching documentation content or accessing specific guides and references.
eldenring.wiki.fextralife.com API
Search and retrieve structured Elden Ring game information from the Fextralife Wiki, including weapons, enemies, locations, and lore. Access full article content with hierarchical sections, tables, and images, or search the complete article catalog by keyword.