Whoami

Use tg whoami to confirm the project and organization for the API key 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
     Project: My Project (proj_xxxxxxxxxxxxxxxx)
Organization: Acme, Inc. (org_xxxxxxxxxxxxxxxx)

The command reads the API key from the TOGETHER_API_KEY environment variable or --api-key flag and reports the project and organization that key is scoped to.

JSON output

Pass --json to get the full structured response, which includes the API key ID and the project slug:

$ tg whoami --json
{
  "api_key_id": "key_xxxxxxxxxxxxxxxx",
  "organization_id": "org_xxxxxxxxxxxxxxxx",
  "organization_name": "Acme, Inc.",
  "project_id": "proj_xxxxxxxxxxxxxxxx",
  "project_name": "My Project",
  "project_slug": "my-project",
  "user_id": "user_xxxxxxxxxxxxxxxx"
}

The project_slug is the DNS-friendly project identifier used when constructing the model value (<project_slug>/<endpoint_slug>) for dedicated endpoint inference calls. user_id is present when the API key is tied to an authenticated user account. It is omitted for service or organization-default keys.

TOGETHER CLI

COMMANDS

JSON output

​JSON output

JSON output