Account Management

Your credits, tokens, and keys. The administrative sacraments.

Commands

Command	Description
`balance`	Check credit balance
`fund`	Show TAO deposit address
`fund list`	List deposit history
`tokens create`	Create API token
`tokens list`	List API tokens
`tokens revoke`	Revoke API token
`ssh-keys add`	Register SSH public key
`ssh-keys list`	List registered SSH keys
`ssh-keys delete`	Delete SSH key

API Tokens

API tokens provide programmatic access for CI/CD pipelines, automation, and server deployments.

Save your token immediately after creation. The full token is only displayed once and cannot be retrieved later.

Set the token via environment variable: export BASILICA_API_TOKEN=basilica_xxxxx

SSH Keys

SSH keys are used to access GPU rental instances. The CLI auto-detects keys from ~/.ssh/ in this order:

id_ed25519.pub
id_ecdsa.pub
id_rsa.pub

Credits & Funding

See Core Concepts for details on how credits work.

Quick start: Run fund to get your TAO deposit address, then send TAO from your Bittensor wallet. Credits are added after 12 block confirmations. Track status with fund list.

Security Best Practices

API Tokens

Use descriptive names (e.g., github-ci, production-server)
One token per service
Rotate regularly
Use environment variables, never hardcode
Revoke unused tokens

Troubleshooting

Insufficient balance

Check balance and fund your account. Use fund list to check pending deposits.

Invalid token

Verify token is set correctly with echo $BASILICA_API_TOKEN. Check if token exists with tokens list. Create a new token if needed.

SSH key not working

Verify key is registered with ssh-keys list. Check local key exists in ~/.ssh/. Re-add if needed.

Next Steps

GPU Rentals: Rent and manage GPU instances
Deployments: Deploy applications
Core Concepts: Understand pricing and billing

On this page