/account
The Account page is tabbed: Profile, Billing, API keys, Validate, Workspaces, Notifications. The selected tab rides the URL (?tab=billing), so links and browser history work. Every form has a visible label and an explicit Save that stays disabled until something changes.
Profile
?tab=profile. Your avatar, name and email come from your sign-in; your title is editable.
Delete account lives here. It deletes everything, immediately: every API and agent key is revoked, so agents stop mid-loop; all connected integrations are disconnected; your interests, projects and history are removed. Type DELETE to confirm. It cannot be undone.
Billing
?tab=billing. One prepaid Remyx balance, spent pay as you go. Validate is the metered agent today; Outrider runs bill your own model provider.
Arriving with
?credits=paid shows that the balance updates once Stripe confirms, usually within a minute; ?buy=credits (the link in a refusal on a PR) opens the top-up flow directly. An account on a grant reads “Covered by a Remyx grant. Tasks are recorded, not charged.”
Full detail, including what admits a validation and when it is charged: Billing.
API keys
?tab=keys. 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 can be scoped, revoked, or deleted at any time. Create one key per machine or workload so you can revoke them independently.
Key types
Creating a key
- Click + Create API key and name it (for example
laptop-cli,ci-experiments). - Pick an expiry: Never expires, 30 days, 90 days, or 1 year.
- Choose access: Full access, or Limited with per-category read/write grants (“write” includes the matching read). One-click presets fill the grid for common workloads. See API Scopes for the catalog, including the new
billingcategory. - 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). Edit changes the name and scopes. Revoke disables a key immediately across the REST API, CLI, and MCP server; it stays listed for audit until you Delete it.
Agent keys
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).
Validate
?tab=validate. Which model writes and repairs validations when you run @remyx-ai validate.
The full resolution order, from a per-call override down to connected providers, is in Validate → Choosing the model.
Workspaces
?tab=workspaces. Projects belong to a workspace; owners and admins manage members and invitations. Expand a workspace to manage member roles (admin, member, read-only), invite by email, and see pending invites. A workspace’s only admin must promote someone else before stepping down, and its projects must be deleted or re-assigned before the workspace can be deleted.
Notifications
?tab=notifications. Your Inbox is the source of truth; email is a mirror of it.
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,
.envfiles 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
Billing
What admits a validation and when it is charged
API Scopes
Scope catalog, presets, and key prefixes
Validate
The agent the Validate tab configures
Connectors
Model-provider keys live there, not here