Registry token

Your registry token unlocks the paid parts of the @chartory registry: types 101–132, Signal, widgets, overlays and the AI Ops template. The 100 free charts need none. Use the licence key from your Code or Complete email, or create your own token in Account · Access, where you can regenerate or revoke it. AI Ops · Code has no licence key: create a token there. The token is your access (your account's Access page shows it too), so keep it out of git and out of client code.

Where it comes from

The purchase email holds two things: the .fig file to download and, for Code and Complete, the licence key, which works as a registry token. Keep the email. Any plan with code can also create a token in Account · Access.

Store it

Put it in .env and keep .env in .gitignore.

CHARTORY_TOKEN=••••••••

.env

Use it

components.json sends it as a header with every request to the registry.

"@chartory": {  "url": "https://usechartory.com/r/{name}.json",  "headers": {    "Authorization": "Bearer ${CHARTORY_TOKEN}"  }}

In CI

Add CHARTORY_TOKEN as a secret in your CI, so builds can install charts.

Keep it private

• Never put it in client code or a NEXT_PUBLIC variable.
• Never commit it to a public repository.
• Share it with your team through your secret store, not in chat.