starred/ALwrity

Fork 0

mirror of https://github.com/AJaySi/ALwrity.git synced 2026-04-25 00:45:54 +03:00

[GH-ISSUE #178] Error in website blog writer #128

New issue

Closed

opened 2026-03-02 23:33:52 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 23:33:52 +03:00

Owner

Originally created by @DikshaDisciplines on GitHub (Apr 23, 2025).
Original GitHub issue: https://github.com/AJaySi/ALwrity/issues/178

Originally assigned to: @uniqueumesh on GitHub.

Hey AJ,
I am getting the below error while using Alwrity 'blog writer' via website.

Failed in metaphor.search_and_contents: Request failed with status code 401: {"requestId":"0a72db55242d79dae320199ab39a38e9","error":"Invalid API key","tag":"INVALID_API_KEY"}

Originally created by @DikshaDisciplines on GitHub (Apr 23, 2025). Original GitHub issue: https://github.com/AJaySi/ALwrity/issues/178 Originally assigned to: @uniqueumesh on GitHub. Hey AJ, I am getting the below error while using Alwrity 'blog writer' via website. Failed in metaphor.search_and_contents: Request failed with status code 401: {"requestId":"0a72db55242d79dae320199ab39a38e9","error":"Invalid API key","tag":"INVALID_API_KEY"} ![Image](https://github.com/user-attachments/assets/a42623b7-fbf0-46e5-a6a9-fa8053e61b3e)

kerem

2026-03-02 23:33:52 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@AJaySi commented on GitHub (Apr 23, 2025):

@uniqueumesh
Request you to have a look and fix it. Thanks.

@AJaySi commented on GitHub (Apr 23, 2025): @uniqueumesh Request you to have a look and fix it. Thanks.

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@uniqueumesh commented on GitHub (Apr 23, 2025):

@AJaySi @DikshaDisciplines

I will check and update here. Thank you for reporting.

@uniqueumesh commented on GitHub (Apr 23, 2025): @AJaySi @DikshaDisciplines I will check and update here. Thank you for reporting.

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@uniqueumesh commented on GitHub (Apr 23, 2025):

@DikshaDisciplines @AJaySi

Thank you for bringing this to our attention. The error you’re encountering is due to the METAPHOR API Key exceeding its free monthly limit of 1000 searches. This is a limitation of the default API key currently configured in the tool.

Update on the Fix:

We’ve recently implemented changes to address this issue. The new update includes:

Custom API Key Input: Users can now provide their own METAPHOR_API_KEY and GEMINI_API_KEY directly in the tool if the default key has reached its limit.
Improved Error Handling: The tool will now provide clearer feedback when the API key limit is exceeded or if the key is invalid.

Before update:

After update:

These changes are in the final stages of review and will be merged and deployed soon. Once deployed, you’ll be able to resolve this issue by either using your own API key.

I appreciate your patience, and we’ll notify you as soon as the update is live!

Best regards

@uniqueumesh commented on GitHub (Apr 23, 2025): @DikshaDisciplines @AJaySi Thank you for bringing this to our attention. The error you’re encountering is due to the METAPHOR API Key exceeding its free monthly limit of 1000 searches. This is a limitation of the default API key currently configured in the tool. ## Update on the Fix: We’ve recently implemented changes to address this issue. The new update includes: - **Custom API Key Input**: Users can now provide their own METAPHOR_API_KEY and GEMINI_API_KEY directly in the tool if the default key has reached its limit. - **Improved Error Handling**: The tool will now provide clearer feedback when the API key limit is exceeded or if the key is invalid. ### Before update: ![Image](https://github.com/user-attachments/assets/64076e32-a9e7-47d0-aadd-f30d75fdc8fd) ### After update: ![Image](https://github.com/user-attachments/assets/046f597a-a7fb-4075-80ec-2f798571507f) ![Image](https://github.com/user-attachments/assets/17c86922-522b-4943-9d7d-cb525e8aeb06) These changes are in the final stages of [review](https://github.com/AJaySi/alwrity_blog_writer/pull/4) and will be merged and deployed soon. Once deployed, you’ll be able to resolve this issue by either using your own API key. I appreciate your patience, and we’ll notify you as soon as the update is live! Best regards

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@uniqueumesh commented on GitHub (Apr 25, 2025):

@DikshaDisciplines

Thank you for reporting this issue and for your patience.

We have resolved the problem by implementing the following updates:

1. Custom API Key Input: Users can now provide their own METAPHOR_API_KEY and GEMINI_API_KEY if the default API key exceeds its limit.

2. Improved Error Handling: The tool now provides clearer feedback when API key limits are exceeded or if the key is invalid.

These updates are live now. You should now be able to use the "blog writer" feature without encountering this issue. If you experience any further problems, feel free to reach out.

Closing this issue as resolved. Thank you for bringing this to our attention!

Best regards

@uniqueumesh commented on GitHub (Apr 25, 2025): @DikshaDisciplines Thank you for reporting this issue and for your patience. We have resolved the problem by implementing the following updates: **1. Custom API Key Input**: Users can now provide their own METAPHOR_API_KEY and GEMINI_API_KEY if the default API key exceeds its limit. **2. Improved Error Handling**: The tool now provides clearer feedback when API key limits are exceeded or if the key is invalid. These updates are live now. You should now be able to use the "[blog writer](https://www.alwrity.com/ai-blog-writer)" feature without encountering this issue. If you experience any further problems, feel free to reach out. Closing this issue as resolved. Thank you for bringing this to our attention! Best regards

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@AJaySi commented on GitHub (Apr 25, 2025):

@uniqueumesh

Do not close issues on your own, give reporter a chance to comment/close.
If the reported does not reply/unresponsive(1-2 days) then you can close it.

@DikshaDisciplines
Are you satisfied with the fix/resolution, related only to what you reported in this issue ?
Thanks.

@AJaySi commented on GitHub (Apr 25, 2025): @uniqueumesh - Do not close issues on your own, give reporter a chance to comment/close. - If the reported does not reply/unresponsive(1-2 days) then you can close it. @DikshaDisciplines Are you satisfied with the fix/resolution, related only to what you reported in this issue ? Thanks.

kerem commented

2026-03-02 23:33:53 +03:00

Author

Owner

@AJaySi commented on GitHub (Apr 26, 2025):

@uniqueumesh
Lets close this as @DikshaDisciplines is unresponsive.
Great job Umesh.

@AJaySi commented on GitHub (Apr 26, 2025): @uniqueumesh Lets close this as @DikshaDisciplines is unresponsive. Great job Umesh.

kerem referenced this issue

2026-03-13 20:22:49 +03:00

[GH-ISSUE #128] package loading is very slow #435

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ALwrity#128

No description provided.

Rows
Columns