Skip to content
Notchset

Pro setup

Pro items come from a private registry. The shadcn CLI sends your personal key with each request, and the files land in your project like any other item. Free items need none of this: install them straight from their URL.

1. Create a key

Sign in at your account with the email you bought with, name the key (for example “Laptop” or “CI”) and select Create key. Copy it right away; it is only shown once. You can keep up to 10 keys and revoke any one of them without touching the others.

2. Store it in your environment

.env.local
NOTCHSET_TOKEN=fmm_your_key_here

Keep .env.local out of git. The shadcn CLI loads it automatically and expands ${NOTCHSET_TOKEN} in components.json.

3. Configure the registry

components.json
{
  "registries": {
    "@notchset": "https://notchset.dev/r/{style}/{name}.json",
    "@notchset-pro": {
      "url": "https://notchset.dev/r/pro/{style}/{name}.json",
      "headers": { "Authorization": "Bearer ${NOTCHSET_TOKEN}" }
    }
  }
}

4. Install

Terminal
npx shadcn@latest add @notchset-pro/password-field @notchset-pro/data-table

Prefer a license-key header? The registry also accepts one:

components.json (registry entry)
"headers": { "X-License-Key": "${NOTCHSET_TOKEN}" }

Every item's AI guide is published at https://notchset.dev/md/<name>.md, and this installs the agent rules for your AI tools:

Terminal
npx shadcn@latest add https://notchset.dev/r/notchset-ai.json

Teams

A Lifetime license is for one developer. A Team license covers up to 10 people: invite teammates from your account; each person signs in with their own email and creates their own token, so you can remove someone without affecting anyone else.

CI and deploys

You only need the token when you add or update items, not to build or run your app: the source is already in your repo. If a script in CI runs the shadcn CLI, create a separate “CI” key and add it as the NOTCHSET_TOKEN secret, so you can revoke it on its own.

Troubleshooting

  • 401 License key missing: NOTCHSET_TOKEN is not set in the shell or .env.local, or the registry is missing from components.json.
  • 403 Key not recognised: the key was revoked or mistyped. Create a fresh one in your account.
  • 403 Not included: your purchase does not cover this piece. The message names the pack, theme or plan that does.
  • 402 Pro item: you used @notchset for a Pro item. Use @notchset-pro.

Still stuck? Email support@notchset.dev.