Rivet CLI

Mint a namespace or deployment secret token from the Rivet dashboard, then use it server-side only. Rivet docs show secret tokens with the sk_ prefix and recommend them for private control-plane access and debugging. You can supply it separately as RIVET_TOKEN with RIVET_NAMESPACE, or embed it in the endpoint URL like https://<namespace>:sk_xxxxx@api.rivet.dev. The CLI can also persist credentials after rivet deploy --token <token>.