
Candor UI docs status
Answered our latest tool-list check 5 hours ago with 12 tools. It will be marked verified after 3 successful checks in 7 days.
- Answered (30 days)
- 2 of 2 checks
- Last seen working
- 17 Nov, 06:16 UTC
- Last commit
- —
- Licence
- Not stated
Live checks
We call this hosted server's tools/list endpoint without credentials, from the public internet, every day while it answers and weekly otherwise.
- Answered
- Needs sign-in
- No answer
| Checked (UTC) | Result | Response time | Tools |
|---|---|---|---|
| 17 Nov, 06:16 | Answered | 2.4 s | 12 |
| 16 Nov, 06:16 | Answered | 2.0 s | 12 |
Tools (12)
Read from the server on 17 Nov 2026.
- search_docs
- Search Candor UI's components, hooks, blocks and patterns by what they do ("approve a tool call", "cost estimate", "session list"). Returns names, tiers and one-line descriptions; read one with get_component_docs.
- get_component_docs
- Read one item's docs as Markdown: what it is, its tier and install command, an example with the import paths an app uses, every prop, function, type, and the LocaleProvider string keys.
- suggest_components
- Describe the screen or feature you're building; get the Candor UI items that fit, why, the matching patterns and screens, and an install command per tier. When nothing in Candor fits, it says so rather than suggesting something close. Pass `sdk` so only your agent SDK's adapter is suggested. Read each suggestion's docs before using it.
- list_components
- List every item by group (Chat, Agent work, App shell, …; the app scaffolding groups, Layout, Charts, Team, Billing and Admin, after the agent groups), or one group's items with descriptions.
- get_pattern
- Read a pattern as Markdown: a common problem in agent UIs (approvals, traces, cost guards, …) and the components that solve it.
- list_screens
- List the screen catalogue by area (talking to the agent, approving and controlling, watching the work, …), one line per screen: what it's for and its slug. Read one with get_screen.
- get_screen
- Read one screen as Markdown: what it's for, two or three layouts with when to pick each, the Candor UI items that build each (with tiers), an install command, the honesty rules that matter most on it, and a brief to hand to the coding agent that builds it.
- get_started
- How to install Candor UI in a React or Next.js app, render a chat, connect an agent SDK, add licensed items and keep them updated. With `prompt: true`, only "Give this to your agent": one block of text for adopting Candor into an app that already exists (it asks about the stack and the agent's API first, installs with the CLI, leaves the licence key to the person and names the providers to wrap th
- get_brief
- One item's brief to hand to the coding agent that builds the screen: the same Markdown the docs page's "Copy for a coding agent" button copies (what the item is, its tier and install command, an example with the import paths an app uses, every prop, the string keys, and the rules to keep).
- get_design
- The design system as Markdown: every colour role and what it's for, the type scale, radius, shadows, motion, density and themes, read from the shipped CSS; how an app re-tokens for its brand; and how to build the screens around Candor components (surfaces, rhythm, writing, do and don't).
- get_review_checklist
- The checklist to run after each screen where an AI agent acts, before moving on: one line per check, each tied to a rule (model output is text, unknown stays unknown, a locked control says why, nothing pre-selected, approve the exact change, reasoning is believed, the app names the agent, say what can be undone, plus status, progress and accessibility). From the candor-agent-ui skill; works with o
- theme_check
- Check a brand file (candor-brand.css, or any CSS that sets Candor's tokens) the way `npx candor-ui theme check` does: colour contrast of every text and edge pairing in light, dark and high contrast, each with its ratio and the ratio it needs, for the base and then for each brand scope ([data-brand="<name>"], as the theme builder writes several brands in one file) as a theme of its own, labelled (L