whoami

Introduction

whoami shows who you are on the SPLENT marketplace and which token the CLI is using. Run it when a publish is refused, or when CI and your laptop disagree.

splent whoami

  Registry   https://marketplace.splent.io (default)
  Identity   dev@example.com
  Scopes     read_spl, write_spl
  Token      splent-cli@laptop
  Expires    2026-10-26T10:00:00+00:00 (in 90 days)
  Source     file /workspace/.splent/credentials.json

The registry line says who chose the marketplace, --registry, SPLENT_MARKETPLACE_URL or default. The source line says where the token came from, the credential file or SPLENT_MARKETPLACE_TOKEN, which always wins. Each registry has its own token, so ask the one you are about to publish to.

When the marketplace does not answer

  Marketplace unreachable at https://marketplace.splent.io
  Connection refused
  You are still logged in locally, this is not a logout.

  Registry   https://marketplace.splent.io (default)
  Identity   dev@example.com (cached)
  ...

Your token is kept. whoami shows the identity it saved last time, marked as cached, and exits 1. A rate limit is reported the same way, with how long to wait.

Reference

Options

Option	Description
`--registry URL`	The marketplace to ask. Defaults to `SPLENT_MARKETPLACE_URL`, then `https://marketplace.splent.io`

Results

It exits 0 only when the marketplace confirms who you are.

What you see	What it means
`Not logged in to <url>`	No token for this registry. Run `login`
`Your marketplace token has expired.` or `... was revoked on the server.`	The stored token is removed, so the next run says not logged in. Log in again
`The token comes from SPLENT_MARKETPLACE_TOKEN, so unset or replace it there.`	The marketplace refused the token in the environment. The CLI never removes that one

A token from SPLENT_MARKETPLACE_TOKEN has no cached identity, since the file describes another token.