# Accounts and Session Keys

> Documentation index: [llms.txt](https://namera.ai/llms.txt).

Source: https://namera.ai/docs/cli/accounts-and-session-keys

Find accounts, inspect permissions, and import a session key.

## Find an Account [#find-an-account]

```sh
namera wallet list
namera wallet get
```

The second command opens an account picker. The CLI uses `wallet` in command
names for the accounts shown in the dashboard.

<div className="docs-response">

```text
👛 Example account | Active
-> Address: 0x1111111111111111111111111111111111111111
-> Network type: EVM
-> Custody: Namera-managed
-> Description: SDK test account
-> Created: 11 Oct 2026, 09:00:00 UTC
```

</div>

## Inspect a Session Key [#inspect-a-session-key]

```sh
namera session-key list --wallet 0199dfe1-0000-7000-8000-000000000001
namera session-key get 0199dfe1-0000-7000-8000-000000000002
```

Replace both IDs with your resources. The detail view separates installed
network permissions from API policies:

<div className="docs-response">

```text
Example session | Active

-> Account: Example account
-> Description: Send 0.001 test ETH on Base Sepolia
-> Created: 11 Oct 2026, 09:05:00 UTC
-> Expires: 11 Nov 2026, 09:00:00 UTC
-> Networks: Base Sepolia

Permissions

Base Sepolia | Installed
-> Starts: 11 Oct 2026, 09:00:00 UTC
-> Message signing: Not allowed
-> Contract access
  Address: 0x2222222222222222222222222222222222222222
-> Native token transfer
  Allowance: 1000000000000000
  Unit: wei

API Policies
-> None
```

</div>

An active key still needs an installed, unexpired authorization on the network
you want to use. A transfer permission does not automatically permit message signing.

## Import an Encrypted Key [#import-an-encrypted-key]

Use the import command provided by the dashboard:

```sh
namera session-key import <encrypted-export> --host https://api.namera.ai
```

Enter the export passphrase when prompted. Import is local and requires no API
login. It saves an encrypted file protected by an independent OS-keyring secret.

<div className="docs-response">

```text
Session key imported
  Status: imported
  Session Key ID: 0199dfe1-0000-7000-8000-000000000002
  Wallet ID: 0199dfe1-0000-7000-8000-000000000001
  Chains: eip155:84532
```

</div>

Import does not install permissions or grant CLI access. Approve a network in
the dashboard, wait for the key to become active, then log in and select it.
Only import keys on machines you trust.

The CLI resolves imported keys automatically when running as the same OS user
against the matching API origin. See
[Import a Session Key](https://namera.ai/docs/cli/reference/session-keys/session-key-import) for
storage and recovery details.

Example output uses fixture accounts and hashes, captured with the CLI's output
formatters. Plain-text output is shown without terminal colors; your values and
relative expiry dates will differ.