devseek
Sign in Get API key

LEVELS

How levels work

Your level decides how many requests may run at the same time. It rises with the tokens you spend on software work and falls when you use devseek for other things. Each step costs more XP than the last.

  1. 2ScriptL1–10Script
  2. 2–3FunctionL11–20Function
  3. 3–4ModuleL21–30Module
  4. 4–5PackageL31–40Package
  5. 5LibraryL41–50Library
  6. 6FrameworkL51–60Framework
  7. 6–7RuntimeL61–70Runtime
  8. 7–8CompilerL71–80Compiler
  9. 8–9KernelL81–90Kernel
  10. 9–10ArchitectL91–100Architect

The ladder

Every 10 levels

LevelRankConcurrent sessionsTotal XP to reachXP to next level
L1ScriptScript20692
L2ScriptScript26921,407
L10ScriptScript223,2914,277
L20FunctionFunction376,9866,585
L30ModuleModule4151,4418,442
L40PackagePackage5243,28210,058
L50LibraryLibrary5350,52711,515
L60FrameworkFramework6471,81412,860
L70RuntimeRuntime7606,13014,116
L80CompilerCompiler8752,68115,302
L90KernelKernel9910,81816,429
L100ArchitectArchitect101,080,000—

Ranks

Every ten levels earn a new rank and mark.

  1. ScriptScriptL1–10
  2. FunctionFunctionL11–20
  3. ModuleModuleL21–30
  4. PackagePackageL31–40
  5. LibraryLibraryL41–50
  6. FrameworkFrameworkL51–60
  7. RuntimeRuntimeL61–70
  8. CompilerCompilerL71–80
  9. KernelKernelL81–90
  10. ArchitectArchitectL91–100

The rules, exactly

  1. Every request that finishes is classified once as coding or not coding. Requests in the same conversation reuse the verdict for up to 20 requests.
  2. Coding: +1 XP per 750 tokens. Not coding: −1 XP per 1,500 tokens. Tokens are the prompt and completion counts reported by the model, never what the client claims. You gain at most 90,000 and lose at most 45,000 XP per day (UTC).
  3. Once a day XP is compared with the ladder. You go up to every level your XP has reached, several at once if you earned enough. If XP falls below 85% of your current level's XP you go down one level, never more than one a day.
  4. On a day with no coding requests XP is multiplied by 0.97.
  5. Level 1 is the floor and level 100 the cap. An operator can set a level by hand; every such change is recorded.
  6. Total XP to reach level L is round(1,080,000 × ((L−1)/99)^1.6). Sessions at level L are 2 + floor((L−1)×8/99).
  7. Each coding request is also graded as a training record. XP multiplier: good ×5, normal ×1, weak ×0, junk ×-1 (junk takes XP away, within the daily loss limit). Weak and junk records are deleted, not stored. A reply where the model showed no text at all is not your fault: it counts as normal and is not stored. The ladder is 20× the original one; XP per token and the daily limits are set so that a heavy daily coder can reach level 100 in about three weeks.

How a request is classified

Clear cases are decided by local rules: code fences, stack traces, diffs, shell commands, file names, tool definitions and programming words. Unclear requests may be sent to jev, a small decision model, as one yes-or-no question built from your request text, up to 240 times a minute for the whole service. If jev is unavailable the local rules decide. The source of every verdict is recorded.