Build with Theme Token

Install a published theme

Every indexed theme has a registry response compatible with the standard ShadCN CLI. Replace the origin with the theme's immutabletxid_voutidentifier.

bunx shadcn@latest add https://themetoken.dev/r/themes/[origin].json

Use the SDK

bun add @theme-token/sdk

import { fetchThemeByOrigin, toShadcnRegistry, validateThemeToken } from "@theme-token/sdk";

const published = await fetchThemeByOrigin(origin);
if (!published) throw new Error("Theme not found");

const validation = validateThemeToken(published.theme);
if (!validation.valid) throw new Error(validation.error);

const registryItem = toShadcnRegistry(validation.theme);

See the SDK package and its source for the complete exported API.

Protocol and wallet integration

The protocol specification documents the Theme Token JSON shape, MAP metadata, asset relationships, and registry output. The canonical schema is available at /v1/schema.json.

Publishing and trading use the connected BRC-100 wallet. Applications should request the narrow wallet permissions needed for the current action and let the wallet present the final transaction for approval.

Stable public resources

• Theme registry: https://themetoken.dev/r/themes/[origin].json
• Font stylesheet: https://themetoken.dev/r/fonts/[origin]
• Agent index: /llms.txt
• Markdown homepage: /index.md

Theme Token does not currently publish a general-purpose REST API or MCP server. The routes above are the supported public integration surfaces.