A typical setup runs 10-15 minutes: account, profile, first route, and optional key setup. The best first route is /challenges — start with a real task before you optimize the rest of the account. Profile, settings, billing, integrations, and API keys all live under /profile, and /skills/prompt-engineering is a strong first public skill loop once your account is active.
Start with one real loop, not every feature at once. The fastest way to understand Versalist is: sign in through your workspace, complete your profile, open one challenge, and only then connect provider keys or CLI tooling if you need them. That keeps the setup grounded in a real use case instead of a checklist with no context. Browse challenges.
Workspace sign-in
Versalist now uses the enterprise sign-in path for new access. Keep your callback destination attached so sign-in drops you into the right workflow instead of a generic landing page.
Continue with SSO
Best for managed workspace access. Enter your work email and Versalist will route you to your company identity provider when one is configured. Open enterprise sign-in.
- Starts from a work email lookup
- Works cleanly with existing callback URLs
- Good default for company-managed access
Use a work provider
If your workspace does not require SSO, you can continue with a Google or GitHub work account from the same sign-in page. Open sign-in.
- Keeps OAuth entry under the enterprise access path
- Pairs naturally with invite links and callback routing
- Works for teams that do not enforce SSO
Request workspace access
If your domain is not configured for SSO yet, the sign-in page lets you request workspace access so onboarding can be coordinated. Request access.
- Designed for company and managed onboarding
- Useful when a team or invite flow is involved
- Keeps billing and workspace setup coordinated
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.
- Open Profile. Set your display name, email, location, public link, and profile visibility basics. Open /profile.
- Review Settings. Check authentication providers, notification preferences, and project visibility defaults. Open /profile/settings.
- Connect integrations only if needed. Bring your own provider keys when you want Versalist to route inference against your own infrastructure. Open /profile/integrations.
- Create a platform key later. Only create a Versalist API key when you are ready for CLI, MCP, or challenge automation flows. Open /profile/api-keys.
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.
Quiz demo
A lightweight way to test whether you understand the basic product and AI workflow concepts. Open quiz demo.
Dashboard and certificates
Use the progress routes to see where your challenge, quiz, and certificate work is accumulating. Open progress dashboard.
Skill path
Open the skill path route when you want a more directed sequence instead of browsing challenges manually. Open skill path.
My skills
Use the skill surfaces to inspect or create skill entries once you start building a stronger learning record. Open my skills.
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.
Challenges
Browse real tasks, start challenge runs, study rubrics, and compare against leaderboards. Open challenges.
AI Tools
Compare model and tool options, then connect the ones you actually use in your workflow. Open AI tools.
Prompt Library
Study prompt structure and keep examples close to the projects, challenges, and evaluations they support. Open prompt library.
Workspace
Organize your tool stack, prompt work, and guided execution surfaces once your workflow starts repeating. Open workspace.
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.
- Day 1: sign in and set the profile shell. Handle workspace sign-in, profile basics, and settings so the logged-in routes feel coherent. Open profile.
- Day 1: browse one challenge and one prompt. Use the public challenge and prompt surfaces to understand the kind of work Versalist organizes. Browse challenges.
- Day 2: inspect the docs and skill routes. Open docs, the prompt engineering skill page, and the quiz or progress routes to build context. Open docs.
- Day 3+: add integrations only when necessary. Connect provider keys or create a platform API key after you know exactly which workflow needs them. Open integrations.