Changelog

Feature release for Parameter Controls, a new setting that allows server bots to add additional input elements to their UI on Poe:

client: add extra_headers to stream_request()

Add a file upload function to client. This should enable file input for bot query requests.

Previously the total length of a bot's response could not exceed 100,000 characters. This has now been updated to 512,000 characters. To see other limits visit https://creator.poe.com/docs/poe-protocol-specification#limits.

The default values on SettingsResponse are changing in the next version of the Poe Protocol, and this updates fastapi_poe to use the new version's functionality:

• New method authorize_cost: used to ensure the user is willing to spend enough points before you make potentially expensive model calls
• New method capture_cost: used to capture the actual cost after you perform the model calls
• New setting cost_label: used to show a short pricing string in the Poe UI (e.g. "100+ points")
• New setting rate_card (previously custom_rate_card): used to provide a more detailed explanation of your pricing structure

Add get_bot_response_sync, which is a synchronous wrapper around get_bot_response. This allows users to call the function more easily without having to worry about asyncio.

Fix an issue with release 0.0.57 where attachments were not made if post_message_attachment was called at the end of get_reponse.

1. Bots can now pass attachments to each other via fp.stream_request. To do this, call the post_message_attachment function, which continues to work like before, but will now also implicitly emit a file event to other server bots calling it. Calling bots will receive the file in the attachment field of a PartialResponse from the bot.
2. OpenAI tool calling improvement: the request will finish without making an extra unnecessary second call to the OpenAI bot if no tools are decided to be called. This saves cost to the user.

This release adds the new DataResponse object which bots can yield to attach a metadata string to their response. This string can be accessed in the metadata field of the associated ProtocolMessage in future requests to the bot. This is useful for storing additional information about previous messages in the conversation.