Pro access

Free blocks need nothing. Pro blocks live behind the same endpoint but require your personal registry token — the proof that you own a license.

Get your token

After buying a plan, sign in with your purchase email. Your account shows a token that starts with bf_. Keep it private — it unlocks every pro block on your behalf.

Use it with the CLI

Point the registry at your token via an Authorization header in components.json — the value is read from an environment variable, so the token itself never lands in your repo:

{
  "registries": {
    "@blockforge": {
      "url": "https://blockforge.terravidhal.me/r/{name}.json",
      "headers": {
        "Authorization": "Bearer ${BLOCKFORGE_TOKEN}"
      }
    }
  }
}

Recommended: a .env.local file

In a Next.js project, put the token in .env.local at the project root. Next and the shadcn CLI read it automatically — nothing to export, it survives across terminal sessions, and .env.local is git-ignored by default:

BLOCKFORGE_TOKEN=bf_your_token

Double-check .env.local is in your .gitignore (it is in a default create-next-app). Never commit your token.

Alternative: export it in your shell

Handy for a one-off install — but it only lasts for the current terminal session:

export BLOCKFORGE_TOKEN=bf_your_token

$env:BLOCKFORGE_TOKEN = "bf_your_token"

Either way, install any pro block exactly like a free one:

npx shadcn@latest add @blockforge/hero-split

Without a valid token, the registry answers 401 for pro blocks and the CLI stops — nothing is downloaded.