feat: add support for Poe and Longcat API endpoints #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request adds support for two new services (
Poe
andLongcat
), in addition to the existing OpenRouter integration. Users can now select the desired backend using the new--poe
and--longcat
options. The script adapts its environment variable checks, API endpoints, and metadata output based on the chosen service.New Service Flags:
--poe
: Use Poe API endpoint (https://api.poe.com/v1/chat/completions)--longcat
: Use Longcat API endpoint (https://api.longcat.chat/openai/v1/chat/completions)Note: The
--provider
flag is now restricted to OpenRouter (shows a warning for other services).Environment Variable Checks:
Requires
POE_API_KEY
for Poe andLONGCAT_API_KEY
for Longcat.Example for LongCat