Honest UI is a React component library with good defaults and no lock-in. Copy components into your project, change the source, and import charts, icons, and visual effects only when you need them.
These examples are interactive previews; they don’t submit data.
or continue with email
Component updates
Changes to components already in your project.
New collections
New charts, icons, and visual tools.
Release notes
A concise summary for every release.
$19/month
$79.99
4.8
View size guide
Free shipping and returns
Two-year extended warranty
or continue with email
Members with access
MIT licensed. Source-first by design.ComparisonsPrivacyAboutContact
Source-first by design
Honest UI separates copied application code from package-backed tools so you can choose the right ownership model for each job. UI and animated components become source files in your repository. Charts, icons, logos, vectors, and shaders remain explicit package imports. The documentation identifies that boundary on every collection instead of treating installation as a single interchangeable step.
Start with a component’s documented structure, states, and styling hooks, then adapt them to the language and constraints of your product. Honest UI supplies the implementation and its design tokens without claiming to know your validation rules, permissions, data, or content. That boundary keeps the starting point useful while leaving consequential product decisions in the application that owns them.
Use the Honest UI CLI when you want component source inside your application. The CLI shows the files and dependencies it plans to add, supports a dry run, and leaves the result under your version control. You can rename the component, change its behavior, or remove it without waiting for a library release. Because the source becomes yours, your team also owns final accessibility, content, testing, and maintenance decisions.
Use the published package for charts, icons, logos, vectors, and shaders when a maintained dependency is the better fit. Each collection has a dedicated import path, which keeps the dependency visible and avoids suggesting that generated assets or rendering systems were copied into your project. The guides document runtime dependencies, reduced-motion behavior, WebGL fallbacks, and the checks your application still needs to perform.
Components use semantic foundations and share a coherent token system for color, type, spacing, radius, effects, and motion. Their final quality still depends on the context around them. Review real content, interaction states, keyboard behavior, focus order, contrast, reduced motion, responsive layout, and failure recovery in the application before treating a composition as complete.
For developers and agents
Everything an integration needs is published at a stable URL and documented as machine-readable data. The REST API and MCP server are read-only and require no account or credential, so you can inspect the registry before writing any code.
The Honest UI REST API v1 exposes the registry catalog, item index, individual items, base colors, and initialization presets as JSON with problem-details errors and versioned lifecycle headers. Generate a typed client from the Honest UI OpenAPI 3.1 specification, which documents every operation ID, parameter description, response schema, error code, and the deprecation policy.
Public GET endpoints: /api/v1/registry for the full catalog, /api/v1/registry/index for valid item names, /api/v1/registry/{name} for one item’s source files, /api/v1/colors/{name} for a base color scale, and /api/v1/init for an initialization preset. Responses carry X-Api-Version, RateLimit-Policy: 600;w=60 fair-use headers, and a Link to the deprecation policy. The API is versioned in the URL path; any future retirement is announced with RFC 9745 Deprecation and RFC 8594 Sunset headers at least 180 days in advance.
Connect an MCP client to the Honest UI MCP server over Streamable HTTP to call typed, read-only tools: list_registry_items takes an optional case-insensitive query substring and returns valid component names with their registry types, and get_registry_item takes an exact returned name and retrieves that item’s source files and dependencies. Call list_registry_items first whenever the name is unknown rather than guessing.
Agents can discover the connection details without manual configuration from the MCP Server Card (SEP-2127) or the domain-level AI Catalog. Both documents are public JSON describing the Streamable HTTP endpoint and its supported protocol versions.
Run npx honestui@latest init to configure a React project, then npx honestui@latest add button to copy a component into your repository with a reviewable file plan and dry-run support. Registry responses follow the shadcn schema, so each item already names its files, npm dependencies, and CSS variables. The honestui package on npm also ships maintained imports for charts, icons, logos, vectors, and shaders.
Point an agent at llms.txt for the curated documentation index, or load the full snapshot from llms-full.txt. Every guide is also available as Markdown by appending .md to its URL, and the Honest UI agent skill describes when and how to install, customize, and verify components. One fetch of the OpenAPI document reveals every machine-readable surface, including the Agent Skills index and the MCP Server Card location.
