shadcnregistry.com APIshadcnregistry.com ↗
Access shadcn/ui registries, components, source code, install commands, and creator data via the shadcnregistry.com API. 8 endpoints for discovery and inspection.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/bf7a9ba5-264f-42cc-9f5e-fa8cbff5fcb2/get_all_registries' \ -H 'X-API-Key: $PARSE_API_KEY'
Get all listed registries from the homepage. Returns registry metadata including name, slug, description, item count, and thumbnail URL.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of registries returned",
"registries": "array of registry objects with name, slug, description, itemCount, thumbnail, and url"
},
"sample": {
"data": {
"total": 84,
"registries": [
{
"url": "https://shadcnregistry.com/8bitcn",
"name": "8bitcn",
"slug": "8bitcn",
"itemCount": 0,
"thumbnail": "https://shadcnregistry.com/_next/image?url=%2Fapi%2Fog%2F8bitcn&w=3840&q=75",
"description": "A set of 8-bit styled retro components. Works with your favorite frameworks. Open Source. Open Code."
}
]
},
"status": "success"
}
}About the shadcnregistry.com API
The shadcnregistry.com API gives developers programmatic access to shadcn/ui component registries through 8 endpoints covering discovery, search, and full component detail retrieval. The get_component_detail endpoint returns file-level source code, npm dependencies, install commands, and registry dependencies for any component by its namespace/name ID. You can also list creators, filter components by type, and inspect arbitrary external registry JSON files.
Registry and Component Discovery
get_all_registries returns every registry listed on shadcnregistry.com, including each registry's name, slug, description, itemCount, and thumbnail URL. From there, get_registry_detail accepts a slug parameter (e.g. 'aceternity' or 'animate-ui') and returns the registry's component list as an array of summaries with id, name, and namespace fields. These IDs are in namespace/name format and feed directly into get_component_detail.
Component Detail and Source Code
get_component_detail is the most data-dense endpoint. Pass a component_id like '@kokonutui/button' and the response includes the full files array — each entry has path, content (source code), type, and target — plus dependencies (npm packages), registryDependencies, installCommand, and a description. This makes it possible to inspect component source without visiting the site.
Search and Filtering
search_components accepts a query string and an optional type filter. The type parameter accepts values such as 'component', 'ui', 'hook', 'block', 'theme', 'page', 'lib', and 'file'. Use get_all_component_types to retrieve the authoritative list of accepted type strings at any time. Each search result includes id, name, description, type, slug, namespace, source, and accessible fields.
Creators and External Registry Inspection
get_creators returns all creators producing shadcn/ui content, with each creator's name and social links across github, youtube, and x. inspect_external_registry lets you pass any external shadcn/ui registry JSON URL and get back structured fields including files, dependencies, devDependencies, categories, schema, and title — useful for auditing third-party registries not indexed on shadcnregistry.com. get_all_components_bulk aggregates full component data across all registries and accepts an optional limit parameter to cap how many registries are processed.
- Build a component search tool that filters shadcn/ui components by type using
search_componentswith thetypeparameter - Automate extraction of component source code and file paths via
get_component_detailfor code generation pipelines - Audit npm dependencies across an entire registry using
get_registry_detailfollowed by bulkget_component_detailcalls - Generate install command scripts for multiple components by collecting
installCommandfields in bulk - Populate a creator directory with GitHub, YouTube, and X profile links from
get_creators - Inspect and validate any external shadcn/ui registry JSON file using
inspect_external_registrywithout manual parsing - Compare component coverage across registries by combining
get_all_registriesitemCounts with per-registry component lists
| 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 shadcnregistry.com have an official developer API?+
What does `get_component_detail` return beyond a component's name?+
files array with each file's path, raw content (source code), type, and target; the installCommand string; dependencies (npm packages); registryDependencies; and a description. You need a component_id in namespace/name format, which you can obtain from get_registry_detail or search_components.Can I retrieve component usage statistics or download counts?+
Does `get_all_components_bulk` return paginated results?+
limit integer to cap the number of registries processed, but it does not expose page/offset pagination. For large-scale collection, use limit to process registries in batches across multiple calls.Is it possible to filter `get_all_registries` by registry category or tag?+
get_all_registries returns all listed registries without a filter parameter; the response includes name, slug, description, itemCount, thumbnail, and url for each. You can fork this API on Parse and revise it to add filtering logic over those fields.