Skip to main content
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.
FieldDescription
NameDisplay name shown in experiment activity feeds and decisions
EmailAccount email (read-only)
RolePrimary role: ML Engineer, Researcher, Data Scientist, Product Leader, or Other
InterestsComma-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:
ColumnDescription
Team NameName of the team
Your RoleOwner, Admin, or Member
ActionsManage members, edit, or delete

​
Projects

A summary of all projects (initiatives) you have access to. Each row shows:
ColumnDescription
Project NameInitiative name
TeamAssociated team
ActionsOpen project, go to settings
Click Create Project to start a new initiative — redirects to Project Settings.

​
API Access

Manage API tokens for programmatic access to Remyx.

​
Remyx API Key

Your primary API key for authenticating with the Remyx REST API, CLI, and MCP server.
ActionHow
GenerateClick Generate to create a new API key
ViewClick the eye icon to reveal the full token
CopyClick the copy icon to copy to clipboard
RefreshClick Refresh to rotate the key (invalidates the previous key)
DeleteClick Delete to revoke the key
Refreshing or deleting your API key immediately invalidates the old one. Any CLI sessions, MCP connections, or scripts using the old key will stop working.
Use this key for: 
# CLI authentication
export REMYXAI_API_KEY=<your-key>

# MCP server connection
{
  "mcpServers": {
    "remyx": {
      "type": "http",
      "url": "https://mcp.remyx.ai/mcp",
      "headers": {
        "Authorization": "Bearer <your-key>"
      }
    }
  }
}

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

​
GitHub PAT

A GitHub Personal Access Token with write access. Used by the implementation pipeline to push branches and open PRs in your repos.
If you’ve connected GitHub via OAuth at Connectors, the OAuth token is used instead of the PAT. The PAT is a fallback for repos where the OAuth app isn’t installed.

​
HuggingFace Token

HuggingFace access token for gated models and datasets.

​
Statsig Console Secret Key

Used for A/B test result integration when Statsig is configured as the testing provider in Project Settings.

​
Security Best Practices

  • Never commit tokens to version control. Use environment variables, .env files (with a loader), or CI secret stores.
  • Rotate keys periodically using the Refresh action.
  • Use OAuth connections (via Connectors) instead of PATs when possible — OAuth tokens are scoped and auto-refreshable.
  • API keys authenticate as your user — any action taken with your key is attributed to your account.

Projects & Settings

Configure initiatives, metrics, and connected tools

Connectors

Connect tools via OAuth instead of PATs

CLI Authentication

Set up the CLI with your API key

API Reference

REST API documentation