Registry Specification
DevClub UI distributes components via an open JSON registry specification that can be consumed by CLI tools, automated agents, or custom build pipelines.
REST Endpoints
The registry exposes clean REST endpoints to search, filter, and fetch component source code programmatically:
Returns all browsable registry components with their full source, the total count, and the list of category ids. Supports query parameters ?category=, ?q=, and ?tag=.
Returns a single component item, including its source files, dependencies, props, and accessibility metadata. Unknown slugs return a 404 with success: false.
Open shadcn-compatible schema catalog. Individual components can be installed directly via npx shadcn@latest add https://ui.devclubxnst.online/r/[name].json.
Status check returning status, version, uptime (seconds since the serving instance started), timestamp, and environment. Use /api/components for component counts.
Registry Item Schema
Each component returned by the API has the following shape. Items also carry the shadcn registry fields $schema, type and title, and each file includes content, type and target.
GET /api/components wraps the items in this envelope:
Categories
ComponentCategory is one of the 19 ids below. Pass the id to ?category=.
buttonsButtons & actions (5)inputsInputs & forms (4)searchSearch & commands (3)navbarNavbar (3)navigationNavigation (4)sliders-and-togglesSliders & toggles (5)menusMenus & overlays (2)cardsCards & testimonials (5)galleries-and-mediaGalleries & media (3)page-transitionsPage Transitions (1)ai-stuffAI & editors (4)charts-and-graphsCharts & graphs (1)displayData & display (5)backgrounds-and-effectsBackgrounds & effects (3)feedbackFeedback & progress (3)loadersLoaders (4)accordionAccordions (3)clocks-and-timersClocks & timers (2)date-and-timeDate & time (1)
Sample Response Payload
Executing a GET request against /api/components/noise produces the following response. It is generated from the live registry data; long strings and arrays are shortened here.
