Agent surface
Inspect and install registry items through HTTP, shadcn manifests, static metadata, and machine-readable docs.
One registry, multiple interfaces
The registry API returns catalog metadata and readable source in a { type, data } envelope. Static shadcn manifests,
agent metadata, and text indexes expose the same catalog in formats suited to their consumers.
HTTP API
List the registry, inspect one item with its dependencies, source files, and anatomy, or search by query. The index links
the complete skin and theme contracts. An item anatomy slice exposes ownScopes for source it owns and installedScopes
for the complete transitive install closure.
# List every registry item (id, kind, summary, install command)curl https://control-ui.dev/api/registry# Read one item — install commands, parsed deps, readable source filescurl https://control-ui.dev/api/registry/chat# Search the registrycurl "https://control-ui.dev/api/registry/search?q=chat"# API responses use the same envelope:# { "type": "item", "data": { … } }# A miss is a 404 carrying a stable code:# { "error": "…", "code": "ERR_UNKNOWN_ITEM", "suggestions": [ … ] }Machine-readable docs
Use the official shadcn catalog, individual item manifests, the concise linked index, the extended reference, or the static agent metadata directly.
# Official shadcn registry cataloghttps://control-ui.dev/r/registry.json# One installable item manifesthttps://control-ui.dev/r/chat-message.json# Concise linked documentation indexhttps://control-ui.dev/llms.txt# Extended catalog, install commands, and practice ruleshttps://control-ui.dev/llms-full.txt# Static agent-friendly registry metadatahttps://control-ui.dev/r/agent-index.json