> ## Documentation Index
> Fetch the complete documentation index at: https://docs.remyx.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Account & keys

> Profile, teams, API keys, agent keys, and where Remyx reaches you

**Nav:** Sidebar > Account (bottom left) | **URL:** [`/account`](https://studio.remyx.ai/account)

The Account page manages your profile, teams, API and agent keys, and email alerts.

***

## Profile

Your avatar, name, and email come from your sign-in; your **title** (e.g. "Staff ML Engineer") is editable and saved as you type.

***

## Teams

Projects belong to a team; owners and admins manage members and invitations. Expand a team to manage member roles (**admin**, **member**, **read-only**), invite by email, and see pending invites. A team's only admin must promote someone else before stepping down, and a team's projects must be deleted or re-assigned before the team can be deleted.

***

<h2 id="api-access">
  API keys
</h2>

Named keys authenticate the CLI, the MCP server, and GitHub Actions — passed as a Bearer token. Keys are shown **once** at creation (Remyx stores only a hash and cannot recover the plaintext) and can be scoped, revoked, or deleted at any time. Create one key per machine or workload so you can revoke them independently.

### Key types

| Prefix   | Type                   | Use it for                                                  |
| -------- | ---------------------- | ----------------------------------------------------------- |
| `rmxu_…` | **Personal**           | Your own CLI, MCP server, and ad-hoc REST calls             |
| `rmxa_…` | **Agent (automation)** | Unattended automation — see [Agent keys](#agent-keys) below |

### Creating a key

1. Click **+ Create API key** and name it (e.g. `laptop-cli`, `ci-experiments`).
2. Pick an expiry: **Never expires**, 30 days, 90 days, or 1 year.
3. Choose access: **Full access**, or **Limited — pick per feature** with per-category read/write grants (GitHub-style; "write" includes the matching read). One-click presets — Read-only, Outrider setup, Experiment CI, Digest bot — fill the grid for common workloads. See [API Scopes](/api-reference/scopes) for the catalog.
4. Copy the key from the show-once modal and use it as `Authorization: Bearer <key>`.

### Managing keys

Each row shows the key's access summary, created / last-used / expiry dates, and its display id (`rmxu_…last4`). **Revoke** disables a key immediately across the REST API, CLI, and MCP server — it stays listed for audit until you **Delete** it. To rotate, create a new key and revoke the old one; keys are immutable once created.

```bash theme={null}
# CLI authentication (personal rmxu_ key)
export REMYXAI_API_KEY=rmxu_xxxxxxxxxxxxxxxxxxxxxxxx

# REST
curl -H "Authorization: Bearer rmxu_xxxxxxxxxxxxxxxxxxxxxxxx" \
  https://engine.remyx.ai/api/v1.0/interests
```

***

<h2 id="agent-keys">
  Agent keys
</h2>

Agent keys (`rmxa_`) are **created and rotated by the agent's Action for each repo** when you provision an agent — you don't mint them by hand. Their scopes are managed by provisioning and can't be edited (rename only).

<Warning>
  **Revoking an agent key pauses that agent immediately** — its next run fails auth. This is the same operation as **Pause** on the [Agents](/platform/agents/overview#run-now--pause) page; resuming requires re-provisioning.
</Warning>

***

## Alerts

Your [Inbox](/platform/review/inbox) is the source of truth; alerts arrive by email, and each teammate sets their own:

| Alert                           | Cadence                                                      |
| ------------------------------- | ------------------------------------------------------------ |
| **Review — Draft PRs ready**    | Email when a draft opens on one of your agents               |
| **Decide — Discussions opened** | Daily digest — these can wait for your morning               |
| **Run failures**                | Immediately when an agent errors                             |
| **Weekly portfolio summary**    | For leads: hit rates, direction signal, and stalled projects |
| **Monthly Mix newsletter**      | Product updates and ML news                                  |

***

## Danger zone

**Delete this account** — this deletes everything, immediately:

* Every API and agent key is revoked — agents stop mid-loop.
* All connected integrations are disconnected.
* Your interests, projects, and history are removed.

Type `DELETE` to confirm. It cannot be undone.

***

## Security best practices

* **One narrowly-scoped key per use.** Grant only the scopes a tool needs; don't reuse one broad key everywhere.
* **Rotate by replacement** — create a new key, revoke the old.
* **Never commit tokens.** Use environment variables, `.env` files (with a loader), or CI secret stores.
* Keys authenticate as you: any action taken with a key is attributed to your account, gated by that key's scopes.

***

## Related

<CardGroup cols={2}>
  <Card title="API Scopes" icon="key" href="/api-reference/scopes">
    Scope catalog, presets, and key prefixes
  </Card>

  <Card title="Agents" icon="robot" href="/platform/agents/overview">
    What provisions and uses agent keys
  </Card>

  <Card title="Connectors" icon="link" href="/platform/configure/connectors">
    Model-provider keys live there, not here
  </Card>

  <Card title="CLI Authentication" icon="terminal" href="/cli#authentication">
    Set up the CLI with a personal key
  </Card>
</CardGroup>