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

Support for poe.com (quora's chatbot service) api #299

Open
knamnguyen opened this issue Mar 25, 2024 · 1 comment
Open

Support for poe.com (quora's chatbot service) api #299

knamnguyen opened this issue Mar 25, 2024 · 1 comment
Assignees
Labels
feature New feature or request P2 Long term work

Comments

@knamnguyen
Copy link

knamnguyen commented Mar 25, 2024

Hey team! I'm using poe.com on their web interface, which:

  • Allows users to create custom bots with unique names
  • 4000 GPT4 messages/month for 20 bucks

With openai api, I'm sending 50 gpt-4 messages/day/4$ ~ 1500 msg/month and it's costing me 100$/month 🥲

Can I propose the feature to support adding poe.com api as an option to access their model through my personal poe.com api key, which will be counted towards my poe.com montly limit?

  • Adding an input field for taking poe.com api key
  • Adding an input field for default bot name to send query to (each bot on poe has a unique name, but I don't think it's possible to retrieve a list of bot names, so an input field to specify which bot to default to would be useful enough already)

Context

import asyncio
import fastapi_poe as fp

# Create an asynchronous function to encapsulate the async for loop
async def get_responses(api_key, messages):
    async for partial in fp.get_bot_response(messages=messages, bot_name="GPT-3.5-Turbo", api_key=api_key):
        print(partial)
 
# Replace <api_key> with your actual API key, ensuring it is a string.
api_key = <api_key>
message = fp.ProtocolMessage(role="user", content="Hello world")

# Run the event loop
# For Python 3.7 and newer
asyncio.run(get_responses(api_key, [message]))

Thank you so much for your hardwork!

@runjinz
Copy link

runjinz commented Mar 27, 2024

We're sorry to have kept you waiting.
After internal discussions, we currently do not have the manpower to support this request.
Thank you for your support.

@knamnguyen

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request P2 Long term work
Projects
None yet
Development

No branches or pull requests

2 participants