shadcnregistry APIshadcnregistry.com ↗
Access shadcn/ui registries, components, source files, and creator data via the shadcnregistry.com API. Search, browse, and inspect components across all listed registries.
What is the shadcnregistry API?
The shadcnregistry.com API provides 7 endpoints for discovering and inspecting shadcn/ui registries, components, and creators indexed on shadcnregistry.com. You can retrieve the full catalog of registries via get_all_registries, fetch every component in a given registry with get_registry_detail, or pull complete source file contents and install commands for any individual component using get_component_detail — all in structured JSON.
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'
Retrieve all listed shadcn/ui registries from the homepage. Each registry includes name, slug, description, item count, and thumbnail URL. No pagination — the full catalog is returned in a single response.
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."
},
{
"url": "https://shadcnregistry.com/aceternity",
"name": "aceternity",
"slug": "aceternity",
"itemCount": 0,
"thumbnail": "https://shadcnregistry.com/_next/image?url=%2Fapi%2Fog%2Faceternity&w=3840&q=75",
"description": "A modern component library built with Tailwind CSS and Motion for React."
}
]
},
"status": "success"
}
}About the shadcnregistry API
Registry and Component Discovery
get_all_registries returns the complete catalog in a single response: each registry object includes name, slug, description, itemCount, thumbnail, and url. From there, get_registry_detail accepts a slug parameter (e.g. animate-ui, magicui, aceternity) and returns every component in that registry — deduplicated across all pages — as an array of summaries with id, name, and namespace. Note that cost scales with registry size, since the endpoint fetches up to 100 pages of 48 components each.
Component Detail and Search
get_component_detail takes a component_id in @namespace/name format (e.g. @kokonutui/button) and returns the full component record: files with path, content, type, and target; tags; categories; repoUrl; websiteUrl; and the install-ready type string. search_components runs a keyword search across all registries and accepts an optional type filter — valid values include component, ui, block, hook, page, lib, file, and theme. The full list of valid type values is available from get_all_component_types.
Creators and External Registry Inspection
get_creators lists every creator on the platform with their name and social links across github, youtube, and x. For components hosted outside shadcnregistry.com, inspect_external_registry accepts any URL pointing to a valid shadcn/ui registry JSON file and returns parsed metadata: name, type, description, dependencies, devDependencies, files with full source content, and categories. This lets you inspect registries that are not yet listed on the main site.
The shadcnregistry API is a managed, monitored endpoint for shadcnregistry.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when shadcnregistry.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 shadcnregistry.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.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a component browser that surfaces source code and install commands from multiple shadcn/ui registries in one place
- Index all components across every listed registry by combining get_all_registries with get_registry_detail for bulk catalog ingestion
- Power a cross-registry search tool using search_components with keyword queries and type filters like 'hook' or 'block'
- Audit npm and registry dependencies for any component using the dependencies and files fields from get_component_detail
- Generate a creator directory with GitHub, YouTube, and X links pulled from get_creators
- Validate or preview any external shadcn/ui registry JSON file by passing its URL to inspect_external_registry
- Filter and categorize components by type using the canonical type list from get_all_component_types
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. 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 the component name?+
path, content (raw source code), type, and target — along with tags, categories, repoUrl, websiteUrl, and the component type string such as registry:component. The component_id must be in @namespace/name format, which you can obtain from get_registry_detail or search_components.Does get_registry_detail handle pagination automatically?+
Can I filter search_components by multiple types at once?+
type parameter currently accepts a single value per request. You can query for each type separately and merge the results. You can fork this API on Parse and revise the endpoint to accept multiple type values and aggregate the results.