Dear NVIDIA Support / Engineering Team,
Hundreds of developers are unable to complete phone verification on build.nvidia.com to generate a NIM API key. Many are truly discouraged and move to other providers. Instead of helping them to ride the wave of innovation, you politely ask them to cope with failing OTP Verification Chain.
Despite exhaustive troubleshooting I performed on a brand-new account with no prior OTP requests or successful verifications, nothing can be done from our end. We are reading polished posts from moderators and hoping for a solution for the classic signature of layer desynchronization. We understand ALL the challenges of such huge company, but NVIDIA… please people!
Reproduction Steps and Observations:
-
Select location and enter a physical mobile carrier number (as shown in attached screenshot #Att1).
-
After processing for a while, the UI displays: “This phone number has exceeded limits, please try a different phone number or try again later.”
-
Network inspection reveals the block originates at the edge reputation service: POST https://api.cloudreputation.nvidia.com/v1/otp/generate Response: { “statusCode”: “TOO_MANY_REQUESTS”, “statusDescription”: “From upstream endpoint https://api.cloudreputation.nvidia.com/v1/otp/generate: local_rate_limited” }
-
On two occasions (after extended waiting and a different session), the edge check was bypassed, an OTP SMS was successfully delivered to the phone, and the verification modal appeared.
-
Entering the received OTP resulted in rejection at the core endpoint: POST https://api.ngc.nvidia.com/v3/otp/verify HTTP 429 (Too Many Requests)
This pattern indicates a desynchronization between the edge WAF/reputation layer and the NGC backend rate-limit store: SMS dispatch occurs, but the persistent state remains locked (race condition plus missing reconciliation logic).
Troubleshooting Already Performed:
-
Clean Incognito session (no cached cookies or local storage).
-
IP rotation and network switch (including cellular tethering) to exclude IP reputation blocks.
-
Confirmed physical SIM-based carrier number (not VoIP).
-
Waited >10 minutes between attempts to allow OTP expiration.
-
No prior registrations or verifications attempted with this number.
Request:
Given that the block occurs on first use and persists even after successful OTP delivery, this appears to be a backend configuration or false-positive reputation issue affecting certain non-US country codes (and recently some US numbers also). I kindly request:
-
Manual reset of the rate-limit state for phone number / account or
-
Temporary whitelist to complete verification
-
Or guidance on an alternative path to API key issuance.
Screenshots attached:
- Verification modal after successful SMS sent, entered OTP + subsequent 429 error in console on /v3/otp/verify and the error message and cleared UI.
- UI with location/phone input and immediate edge block JSON response from api.cloudreputation.nvidia.com.
This issue prevents legitimate developer access to NIM inference capabilities, for too many people and for too many months. Thank you for your prompt assistance.
0xdadc
Att1
Att2
