Whoami

Show the project and organization for the credentials the Together CLI uses.

Use tg whoami to confirm the project and organization for the credentials the CLI uses. This helps when you manage multiple API keys or switch between projects and need to verify the active context before running a command that creates or modifies resources.

tg whoami

Sample output:

$ tg whoami
     API key: key_xxxxxxxxxxxxxxxx
     Project: My Project (proj_xxxxxxxxxxxxxxxx)
Organization: Acme, Inc. (org_xxxxxxxxxxxxxxxx)

The command uses the same credentials as every other CLI command: the --api-key flag, then your tg login session, then the TOGETHER_API_KEY environment variable. When you’re logged in, the first line shows your user ID instead of an API key ID.

JSON output

Pass --json to get the full structured response, which includes the project slug:

$ tg whoami --json
{
  "type": "project_api_key",
  "api_key": {
    "id": "key_xxxxxxxxxxxxxxxx"
  },
  "organization": {
    "id": "org_xxxxxxxxxxxxxxxx",
    "name": "Acme, Inc."
  },
  "project": {
    "id": "proj_xxxxxxxxxxxxxxxx",
    "name": "My Project",
    "slug": "my-project"
  }
}

The type field shows which kind of credential the CLI used, such as project_api_key for an API key or user_org_project_jwt for a tg login session scoped to a project.

The project slug is the DNS-friendly project identifier used when constructing the model value (<project_slug>/<endpoint_slug>) for dedicated endpoint inference calls.