Skip to content

Onboarding blocked: Unable to generate NVIDIA API key on build.nvidia.com — account verification + org permissions issues #201

Closed as not planned

Description

@Kenmege

Problem

The NemoClaw onboarding wizard (nemoclaw onboard) requires an NVIDIA API key from build.nvidia.com, but the key generation flow has multiple blockers that prevent completing setup.

Environment

  • NemoClaw: installed from source (latest main branch)
  • Platform: Brev cloud instance (Ubuntu, 4 CPU / 16 GiB, GCP Iowa)
  • OpenShell: 0.0.8-dev.1+g0463046
  • Node.js: v24.14.0

Steps to Reproduce

  1. Deploy NemoClaw via Brev launchable (env-3Azt0aYgVNFEuz7opyx3gscmowS)
  2. Fix cgroup v2 issue (manually set "default-cgroupns-mode": "host" in daemon.json)
  3. Run nemoclaw onboard
  4. Wizard prompts for NVIDIA API key
  5. Navigate to build.nvidia.com to generate a key

Issues Encountered

  1. Rate limiting on key generation: Received "number has requested too many" error despite not having previously requested keys
  2. Verification code error: After eventually receiving a verification code, got an error message advising to contact support
  3. Organization permissions: After login, the API Keys page shows:

    "No API Key Permissions — You do not have permissions to create API Keys in this Organization. Switch Orgs or contact your admin."

  4. Account verification gate: Prompted with "Please verify your account to get API access" with no clear path forward

Expected Behavior

A new NVIDIA account should be able to generate an API key from build.nvidia.com without being blocked by org permissions or unresolvable verification loops.

Suggestions

  • Document known API key provisioning delays or requirements in the Prerequisites section
  • Add a preflight check in nemoclaw onboard that validates API key access before running the full wizard
  • Consider supporting --skip-api-key flag for users who want to complete setup and add the key later
  • Clarify which NVIDIA org/account type is required (personal vs. enterprise)

Workaround

None found yet. Onboarding cannot proceed without a valid API key.

Activity

  1. kjw3 commented on Mar 17, 2026

    @kjw3
    Contributor
  2. nv-kasikritc commented on Mar 17, 2026

    @nv-kasikritc
    Contributor

    Hi @Kenmege ,

    If you’re having issues verifying your account on build.nvidia.com, please send an email to help@build.nvidia.com

    Be sure to include:

    1. the email address you registered with on build.nvidia.com
    2. any phone number(s) you tried to verify
    3. details of any error message you received (including a screenshot)

    Best,
    Gus

  3. wildhuman commented on Mar 18, 2026

    @wildhuman

    Same issue here

  4. redlock commented on Mar 18, 2026

    @redlock

    yep me too just created a cloud account.

  5. tony33-code commented on Mar 19, 2026

    @tony33-code

    @nv-kasikritc I have sent the email

  6. geekynasir commented on Mar 28, 2026

    @geekynasir

    same my phone no doesn't work

  7. wscurran commented on Apr 22, 2026

    @wscurran
    Contributor

    Thanks for raising this — account verification and API key generation on build.nvidia.com is managed by NVIDIA's platform team and falls outside the NemoClaw project scope. For access issues, please reach out to NVIDIA developer support at developer.nvidia.com/support. Closing here to keep the queue focused on NemoClaw itself.

  8. added
    area: installInstall, setup, prerequisites, or uninstall flow
    area: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flow
    and removed on Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: installInstall, setup, prerequisites, or uninstall flowarea: onboardingOnboarding FSM, provider setup, sandbox launch, or first-run flowplatform: brevAffects Brev hosted development environments

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions