User Manual    [Previous]   [Next]   

Help with AI keys

This page helps you understand how AI keys work in UmpleOnline, and what to do when you see errors such as Provider error or Rate limited.

Important: UmpleOnline uses a BYOK (bring-your-own-key) approach. Your AI key is stored in your browser's local storage and is never sent to Umple servers. Your browser sends requests directly to the AI provider you selected.

1. What does "Verify key" do?

• Verify key checks that the key you entered is accepted by the selected provider.
• If verification succeeds, UmpleOnline enables the model list and lets you choose a model.
• Verification status is stored in your browser's local storage. In normal browsing mode it should persist across page reloads and future sessions on the same browser/computer.

2. Common errors and what they mean

• Authentication failed. Please check your API key.

  The provider rejected your key. Common causes:

  • The key was pasted incorrectly (extra spaces, missing characters).
  • The key belongs to a different provider than the one selected.
  • The key was revoked or expired in the provider dashboard.

• Rate limited (...). Please retry shortly.

  This means the provider (or an upstream provider behind OpenRouter) temporarily rejected requests because too many requests are happening in a short time. What to do:

  • Wait and retry.
  • Switch to a different model (often the fastest fix).
  • OpenRouter may prompt you to set up your own integration key. This means the upstream provider behind OpenRouter is rate-limiting requests. Users are being asked for a BYOK setup because it is assumed that no providers are currently available for the selected model. Consequently, users must upload an API key from their own chosen provider to continue using it.

3. Tips for reliable use

• Providers prefer paid users: Free tier users might reach their threshold easily compared to paid users.
• Switch models when blocked: With OpenRouter, multiple upstream providers may exist behind a model, and availability can change minute-to-minute.
• If verification seems to "reset": check whether your browser is clearing local storage (private mode, strict tracking protection, storage cleaners, etc.).