Pro license
Buy a plan, create a key, and install the paid blocks.
Pro blocks are served by a registry that checks a license key. The key is an API key from your Wobko account, and the account needs an active plan.
1. Get a plan
Choose a plan on the pricing page and sign in when asked.
2. Create a key
In your account, open Settings, then API keys, and create a key. Copy it when it is shown. You cannot see it again later.
3. Put the key in your environment
The CLI reads the key from WOBKO_LICENSE_KEY.
export WOBKO_LICENSE_KEY="your-key"On Windows PowerShell:
$env:WOBKO_LICENSE_KEY = "your-key"Keep the key out of git
Do not write the key into components.json. The file only names the variable. Anyone with the key can install the Pro blocks on your account.
4. Add the Pro registry
Add a second entry next to the free one:
{
"registries": {
"@wobko": "https://wobko.dev/r/{name}.json",
"@wobko-pro": {
"url": "https://wobko.dev/api/registry/pro/{name}",
"headers": {
"Authorization": "Bearer ${WOBKO_LICENSE_KEY}"
}
}
}
}5. Install
npx shadcn@latest add @wobko-pro/pricing-01A Pro block depends on free components. The CLI gets those from @wobko and the block itself from @wobko-pro, so keep both entries.
In CI
Add WOBKO_LICENSE_KEY as a secret in your CI provider and expose it to the step that runs the shadcn CLI. You only need it when a job installs blocks. A normal build does not use it, because the blocks are already source files in your repository.
Errors
| Response | Meaning | What to do |
|---|---|---|
| 401 | The key is missing or not valid | Check that the variable is set in the shell that runs the CLI, and that the key was not deleted |
| 403 | The key is valid but its account has no active plan | Check Billing in your account settings |
| 404 | No Pro item has that name | Check the name in the catalog. Free blocks install from @wobko |