# div whoami

> Which org this machine acts for, which key it uses and who made it, where the key was found, and which control plane it talks to.

```bash
div whoami
div whoami --json
```

```text
Divergent (divergent)  Compute Pro  $243.12 of credit
key   div on MacBook-Pro.local  dv_live_q6Y9NTBb…  made by founder@divergentlabs.xyz
from  ~/.config/divergent/config.json
api   https://api.divergentlabs.xyz
```

Four facts, because the question is usually "why is this command hitting the wrong org?", and any one of them can be the answer. The first line also names the org's plan, Free or Compute Pro, since that is what decides how much it can hold at once. Only the key's prefix is printed.

## Flags

| Flag | What it does |
| --- | --- |
| `--json` | print `GET /me` as the API sent it |
| `--token <key>` | ask about this key instead of the one configured |
| `--api-url <url>` | ask this control plane instead |

## The from line

`from` says where the key was found: `--token`, `DIVERGENT_API_KEY`, `DIVERGENT_TOKEN`, or the settings file — the answer when a fresh `div login` is still hitting the old org, because `DIVERGENT_API_KEY` is set in the shell.

[Configuration](https://docs.divergentlabs.xyz/compute/cli/configuration.md) has the whole order of precedence.