Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

README: Explain OpenAI billing for API key (Fixes issue about "API Rate Limit Reached. Waiting 20 seconds ... Failed to get response after 5 retries") #1304

Merged
merged 1 commit into from
Apr 15, 2023

Conversation

JuroOravec
Copy link
Contributor

Background

There's multiple issues, where people hit OpenAI API rate limiting error, where the true cause of the rate limiting is that people have not set up billing (paid account) on their OpenAI profile.

The truth is, one has to:

  1. Opt in to "paid account" on https://platform.openai.com/account/billing/overview and enter their billing info
  2. Only now request the API key (in my case it took about 5-10 mins after opting into paid account before the API key started to work via AutoGPT.

As of 12:00 14/04/2023, I found these related issues:

Examples:

Possibly also

Changes

Make this explicit in the README file. I've moved the sentence on OpenAI API key to it's own section, so we can also include an image showing exactly what one has to do

Screenshot 2023-04-14 at 12 32 56

Documentation

Test Plan

PR Quality Checklist

  • My pull request is atomic and focuses on a single change.
  • I have thoroughly tested my changes with multiple different prompts.
  • I have considered potential risks and mitigations for my changes.
  • I have documented my changes clearly and comprehensively.
  • I have not snuck in any "extra" small tweaks changes

@JuroOravec
Copy link
Contributor Author

CC @Torantulino

(Or @nponeccop, are you a maintainer too? Because I just saw that you were active around :D)

@JuroOravec
Copy link
Contributor Author

JuroOravec commented Apr 14, 2023

And this is how the README section looks with the change

Screenshot 2023-04-14 at 13 45 58

@nponeccop
Copy link
Contributor

@JuroOravec I'm not but I'm coordinating the merges and do preliminary reviews and conflict resolution notifications. The maintainers are @p-i- and @richbeales and @Torantulino obviously.

@dhruv-programmes
Copy link

Sent a pull request which shows the error regarding the billing problem (but only in debug mode) ,there are more errors which are not shown in detail. Would love to see more updates regarding this problem .

Copy link

@jpollard-cs jpollard-cs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thank you for also doing the cleanup work!

@DrReefer
Copy link

I have set up a paid openai and still get the error Warning: The file 'auto-gpt.json' does not exist. Local memory would not be saved to a file.
Please set your OpenAI API key in .env or as an environment variable.
You can get your key from https://beta.openai.com/account/api-keys

@nponeccop nponeccop mentioned this pull request Apr 14, 2023
1 task
@richbeales richbeales merged commit 5e18bb4 into Significant-Gravitas:master Apr 15, 2023
@KunLiam
Copy link

KunLiam commented Apr 16, 2023

这就是 README 部分在更改后的样子

屏幕截图 2023-04-14 at 13 45 58

OpenAI can set up paid accounts, is there a limit for the region, which regions can set up?

@anonhostpi anonhostpi added API access Trouble with connecting to the API API costs Related to monitoring/reduction of running costs labels May 11, 2023
sindlinger pushed a commit to Orgsindlinger/Auto-GPT-WebUI that referenced this pull request Sep 25, 2024
README: Explain OpenAI billing for API key (Fixes issue about "API Rate Limit Reached. Waiting 20 seconds ... Failed to get response after 5 retries")
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API access Trouble with connecting to the API API costs Related to monitoring/reduction of running costs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants