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.

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.

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.

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.

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.”

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.