Your account home at /profile holds personal details, public identity, and the summary shell for account work. /profile/settings covers authentication providers, notifications, and visibility defaults. /profile/billing handles plans, invoices, credits, and customer-portal actions. /profile/api-keys manages scoped keys for the Versalist CLI, MCP, and challenge APIs.
Platform keys and provider keys are not the same thing. Versalist platform keys authenticate against Versalist itself for CLI, MCP, and challenge submission APIs. Provider keys live in Integrations and tell Versalist which external model vendors it can use on your behalf. Keep those mental models separate. Open integrations.
Profile surfaces
The profile module is the control plane for your identity in the product. These routes should stay lightweight and current so your prompts, projects, skills, and public-facing surfaces all inherit the right context.
Profile overview
Update your name, email, location, public link, and avatar behavior from the main profile route. Open profile.
Settings
Review linked authentication providers, notification preferences, and project visibility defaults. Open settings.
Integrations
Add or rotate provider credentials when you want Versalist to use your own OpenAI, Anthropic, Google, Azure, or Bedrock setup. Open integrations.
API keys
Create scoped platform keys once you are ready for CLI, MCP, or automated challenge submission flows. Open API keys.
Account and security routines
Most users only need a few repeated account habits: keep the profile shell correct, review linked providers, and rotate credentials when your workflow changes. Treat these routes as maintenance surfaces rather than places you live in every day.
- Keep your profile details current. Name, email, location, and public link flow into your logged-in surfaces and shared work. Update profile.
- Review linked providers. Use settings to confirm Google, GitHub, and related auth providers are attached the way you expect. Review linked providers.
- Tune notifications deliberately. Newsletter and workflow notifications should support the loops you actually use instead of becoming noise. Manage notification settings.
- Rotate keys instead of reusing them forever. Provider keys and platform keys should be named, scoped, and replaced when your environment changes. Manage platform keys.
Platform keys
Platform keys are for Versalist workflows, not direct model-provider access. Use them when you want scripts, repos, editors, or agents to authenticate against the challenge and submission APIs without relying on a browser session.
Least-privilege access
Choose only the scopes the environment needs: challenge reads, submissions, or submission-history access. Read API key docs.
- read:challenges for listing and loading challenge content
- submit:solutions for posting challenge runs
- read:submissions for reviewing your own run history
Create, reveal once, revoke
The plaintext key is shown once, last-used timestamps are tracked, and revocation is immediate. Manage API keys.
Attach keys to local workflows
Export the key into your shell or editor environment when you are using the CLI or MCP mode. Open CLI docs.
Billing and plan management
Billing is where you manage plan state, invoices, credits, and customer-portal actions. Keep it operational: review what plan is active, what renews when, and whether credits or provider integrations should carry the next workload.
Subscription status
The billing page surfaces your current plan, renewal state, cancellation status, and any checkout return state. Open billing.
Credits and paid features
Billing can include credit purchases and free-tier status checks, which matter when you are moving beyond casual usage. Review credits and usage.
Invoices and customer portal
Use billing to inspect past invoices or hand off payment-method updates to the customer portal. Review invoices.
Notifications and visibility
Settings controls both operational noise and public posture. The right goal is not “turn on everything”, but “leave on the channels that actually support your build loop.”
Notification preferences
Use settings to decide whether product and newsletter updates support your workflow or distract from it. Open notification settings.
Project visibility
Review how your work is exposed so public-facing routes match the level of sharing you intend. Review visibility settings.
Support paths
Use support and feedback routes when an issue is operational, not something you should solve by editing settings repeatedly. Open support FAQ.
Data export and deletion
Sensitive or destructive account operations should be handled deliberately. If you need help with account export, deletion, or a privacy-sensitive request, use support instead of assuming there is a hidden self-serve destructive path.
Use support for export, deletion, or account recovery questions. For account deletion, privacy-sensitive changes, or export requests that should not be handled through normal profile editing, contact support@versalist.com. That keeps destructive account work explicit and reviewable.