Configuration
Authenticate the CLI.
Configuring tokenolo comes down to one thing: authenticating the CLI against your account.
Note: the CLI is pre-release. Use the exact mechanism shown on your API keys page and by
tokenolo --help; the shapes below reflect the current onboarding flow.
Authenticate
Create an account at app.tokenolo.com/signup,
generate an API key (tk_live_…) from the dashboard, then link the CLI to it:
tokenolo login --key tk_live_…
You can also run tokenolo login on its own and paste the key at the prompt.
Either way, this connects the CLI to your account so runs count against your
plan's daily quota.
Non-interactive auth
For CI or headless environments, pass the key straight to login --key — it's
already non-interactive, so no prompt is involved. Keep the key in your CI's
secret store and reference it:
tokenolo login --key "$TOKENOLO_CI_KEY"
Here TOKENOLO_CI_KEY is a secret you set in CI. The CLI does not read any
key from the environment automatically — it only uses the key you hand to
--key (or paste into tokenolo login).
Warning: never commit a
tk_live_…key to source control. Keep it in your CI's secret store, and rotate it from the dashboard if it leaks.
Next steps
- Quickstart — install, authenticate, and wrap your first session.
- tokenolo wrap — the core command and its options.