Account, profile, first route, and optional key setup.
Start with a real task before you optimize the rest of the account.
Profile, settings, billing, integrations, and API keys live here.
A strong first public skill loop once your account is active.
Create your account
Versalist supports both individual and enterprise entry paths. Choose the route that matches how you plan to use the product, then keep your callback destination attached so sign-in drops you into the right workflow instead of a generic landing page.
Complete your profile
Once you are authenticated, do the minimal profile setup that improves recommendations and makes the logged-in surfaces more useful. You do not need to fill every field before starting a challenge, but the account shell is much more coherent after these basics.
Assess your baseline
Versalist does not force a long onboarding wizard before you can do useful work. Instead, use the learning and progress routes to benchmark what you already know and decide which loop should come next.
Explore the main product surfaces
Most users only need four surfaces to begin: challenges for real tasks, prompt and tool surfaces for study, docs for reference, and workspace for organizing the work once it becomes repeatable.
Free vs paid usage
The important distinction is not “can I look around?” versus “can I do anything useful?”. The product is designed so public browsing and early learning start immediately, while higher-volume or more advanced workflows sit behind account, billing, or BYOK setup.
| Capability | Public / free entry | Paid or advanced setup |
|---|---|---|
| Discovery | Browse public docs, skills, prompt examples, tool directory, and challenge listings. | Use billing and credits once you want sustained or team-scale usage. |
| Execution | Start with public routes, guided learning paths, and selected product surfaces. | Unlock heavier logged-in workflows, billing-backed usage, and company operations. |
| Integrations | You can inspect docs and product flows without attaching provider credentials. | Bring your own provider keys or platform API keys when you need automation or infra control. |
| Proof of work | Build an initial public record through challenges, prompts, and progress surfaces. | Use billing, certificates, and expanded logged-in workflows when the work becomes more serious. |
Recommended first week
If you want the shortest path to meaningful value, use this sequence. It keeps the account work proportional to what you are actually trying to learn or ship.