mzizi.dev/components/<name>. The API endpoints below cover
the same ground from a script.
Install any component
List programmatically
/v1/ui/{name}/docs answers with the component’s use cases, variants and accessibility notes.
/v1/ui/{name}/versions answers 503, because version history is console data; see
the API gateway for why.
The index response is a shadcn registry document: components sit under items, each with
name, type and description. The per-component response adds the full source in
files[].content.
The index is not an array.
GET /v1/ui returns { "$schema": …, "name": "mzizi", "homepage": …, "items": [ … ] }, and a client that decodes it as a bare list decodes it to
nothing — which then renders as an empty gallery rather than an error. This has bitten a
real consumer; decode the envelope.Naming
Component naming is a deliberate mix. Framework-standard primitives keep their plain shadcn names —button, dialog, card — while many brand composites carry the mzizi- prefix.
Components once named nyuchi-* were renamed mzizi-* on 27 September 2026, and the old
names answer 308 to the new ones.