API
The HextaUI HTTP API and OpenAPI spec: registry and docs endpoints, authentication with sessions and API tokens, Pro blocks and error responses.
Everything on HextaUI is also available over HTTP. The registry and docs are static JSON and Markdown files that need no key. Account and Pro endpoints use your sign-in session or an API token.
Assistants that speak MCP can use the same data as tools through the HextaUI MCP server instead.
OpenAPI spec
The HextaUI API is described by an OpenAPI 3.1 document at https://hextaui.com/openapi.json. Every operation has an operationId, typed parameters and response schemas, so you can generate a client or hand it to an agent as function-calling tools.
Public endpoints
GET /r/registry.jsonlists every registry item.GET /r/{name}.jsonreturns one item with the full source of each file.GET /mcp/index.jsonlists every component, hook, utility and guide with its category, description and examples.GET /docs/{slug}.mdreturns a docs page as Markdown./llms.txtlinks to all of them.GET /api/md/{path}returns any public page as Markdown, the same file as/{path}.mdor a request withAccept: text/markdown.GET /api/md/_cataloglists every one.POST /mcpis the Streamable HTTP endpoint of the MCP server.
Authentication
Sign in with GitHub or Google on the account page. The browser then holds a session cookie that the account endpoints read. Only pages on hextaui.com can call the endpoints that change something.
Pro accounts can create API tokens on the same page. Send one as Authorization: Bearer hxt_… to install Pro blocks from the shadcn CLI or a script.
The token rules are published as protected-resource metadata at https://hextaui.com/.well-known/oauth-protected-resource. A 401 from a Pro endpoint links to it in its WWW-Authenticate header.
Account endpoints
GET /api/accountreturns whether the account has Pro, on which plan, and which providers are linked.POST /api/checkoutstarts a Solo or Team checkout and returns its URL. No session is needed.POST /api/claimconfirms a payment from its checkout return link and, when signed in, moves an unclaimed purchase to the account.GET /api/tokensandPOST /api/tokenslist and create API tokens.DELETE /api/tokens/{id}deletes one.GET /api/teamandPOST /api/teamlist and add teammates on a Team plan, andDELETE /api/team/{id}removes one.GET /api/auth/get-sessionreturns the current session, ornull.
Pro endpoints
GET /r/pro/{name}.jsonreturns a Pro block as a shadcn registry item. Free blocks, like Prompt Input, need no token.GET /api/pro/blocks/{name}returns the source files of a Pro block.
Errors
Errors use RFC 9457 problem details with the application/problem+json type. Each one has a stable code, a detail that says what went wrong and a resolution that says how to fix it.
bad_request(400): Bad request.invalid_signature(401): Invalid signature.forbidden(403): Forbidden.pro_required(403): HextaUI Pro required.not_found(404): Not found.method_not_allowed(405): Method not allowed.token_limit(400): Token limit reached.seat_limit(400): Seat limit reached.team_required(403): Team plan required.sponsor_slot_taken(409): Sponsor slot booked.upstream_error(502): Upstream service failed.
SDK and tools
There is no separate SDK package. The shadcn CLI is the client for the registry, the MCP server is the client for assistants, and the OpenAPI spec generates a typed client in any language.