Account & API Keys

Nav: Sidebar > Account (bottom left) | URL: /account The Account page manages your Remyx identity, team memberships, and API credentials.

Profile

Your profile helps Remyx personalize recommendations and set up your workspace.

Field	Description
Name	Display name shown in experiment activity feeds and decisions
Email	Account email (read-only)
Role	Primary role: ML Engineer, Researcher, Data Scientist, Product Leader, or Other
Interests	Comma-separated list of topics you work on — used as default context when you haven’t created Research Interests yet

Click Save to update your profile.

Teams

Teams group users for shared project access and experiment visibility.

Creating a Team

Click Create Team and provide a team name. You’re added as the owner.

Team Management

The Teams table shows:

Column	Description
Team Name	Name of the team
Your Role	Owner, Admin, or Member
Actions	Manage members, edit, or delete

Projects

A summary of all projects (projects) you have access to. Each row shows:

Column	Description
Project Name	Project name
Team	Associated team
Actions	Open project, go to settings

Click Create Project to start a new project — redirects to Project Settings.

API Access

Manage named API keys for programmatic access to Remyx. You can create as many keys as you need (one per tool, environment, or automation), each with its own scopes and status.

Key types

Every key carries a prefix that tells you what it’s for:

Prefix	Type	Use it for
`rmxu_…`	Personal	Your own CLI, MCP server, and ad-hoc REST calls. Never expires.
`rmxa_…`	Automation	Unattended automation. Provisioning automated discovery PRs mints these into repo secrets; CI uses them. Expires after 365 days.

Both are opaque tokens (prefix + random entropy + checksum). Remyx stores only a SHA-256 hash, never the plaintext.

Creating a key

Click Create API Key and give it a descriptive name (e.g. laptop-cli, ci-experiments).

Choose its scopes: either pick individual scopes from the catalog or apply a one-click preset:

Preset	Grants
Read-only	Read access across the catalog
Outrider setup	`provisioning:write`, `interests:write`, `github:write`, … (for automation keys)
Experiment CI	`experiments:write`, `evals:write`, `projects:read`
Digest bot	`recommendations:read`, `papers:read`, `interests:read`

Click Create. The full token is shown once.

The plaintext token is displayed only at creation. Copy it immediately; Remyx cannot show it again. Afterward the key is rendered as rmxu_…last4 for identification only.

See API Scopes for the full scope catalog and what each preset grants.

Managing keys

Each key row shows its name, prefix/last-4, scopes, status, and last used timestamp.

Action	Effect
Revoke	Soft-disables the key immediately. It stops authenticating but stays in the list for audit.
Delete	Hard-removes the key permanently.

Revoking or deleting a key takes effect immediately across the REST API, CLI, and MCP server. Any session or script using that key stops working at once.

Using a key

# CLI authentication (use a personal rmxu_ key)
export REMYXAI_API_KEY=rmxu_xxxxxxxxxxxxxxxxxxxxxxxx

# MCP server connection
{
  "mcpServers": {
    "remyx": {
      "type": "http",
      "url": "https://mcp.remyx.ai/mcp",
      "headers": {
        "Authorization": "Bearer rmxu_xxxxxxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

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

HuggingFace token

HuggingFace access tokens for gated models now live on the HuggingFace integration connection. Set them via Connectors.

Security Best Practices

Use a narrowly-scoped key per use. Create a separate key for each tool or automation and grant it only the scopes it needs. Don’t reuse one broad key everywhere.
Rotate by replacement. To rotate, create a new key and revoke the old one. (There is no in-place refresh; keys are immutable once created.)
Never commit tokens to version control. Use environment variables, .env files (with a loader), or CI secret stores.
Prefer automation keys (rmxa_) for unattended use. Their 365-day TTL limits exposure if a secret leaks.
API keys authenticate as your user; any action taken with a key is attributed to your account, gated by that key’s scopes.

Project Settings

Configure projects, metrics, and connected tools

Connectors

Connect tools (GitHub, HuggingFace, …) via OAuth

API Scopes

Scope catalog, presets, and key prefixes

CLI Authentication

Set up the CLI with your API key

API Reference

REST API documentation

Introduction

Discover

Experiments

Manage

Admin

Concepts

Roadmap

Account & API Keys

Profile

Teams

Creating a Team

Team Management

Projects

API Access

Key types

Creating a key

Managing keys

Using a key

HuggingFace token

Security Best Practices

Project Settings

Connectors

API Scopes

CLI Authentication

API Reference

​Profile

​Teams

​Creating a Team

​Team Management

​Projects

​API Access

​Key types

​Creating a key

​Managing keys

​Using a key

​HuggingFace token

​Security Best Practices

​Related

Project Settings

Connectors

API Scopes

CLI Authentication

API Reference

Profile

Teams

Creating a Team

Team Management

Projects

API Access

Key types

Creating a key

Managing keys

Using a key

HuggingFace token

Security Best Practices

Related