-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Update docs and models files to reflect Perplexity supported models (November 2024) #6888
base: main
Are you sure you want to change the base?
Conversation
… of november 2024
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've completed my review and didn't find any issues... but I did find this rooster.
\\
(o>
\\_//)
\_/_)
_|_
Need a new review? Comment
/korbit-review
on this PR and I'll review your latest changes.Korbit Guide: Usage and Customization
Interacting with Korbit
- You can manually ask Korbit to review your PR using the
/korbit-review
command in a comment at the root of your PR.- You can ask Korbit to generate a new PR description using the
/korbit-generate-pr-description
command in any comment on your PR.- Too many Korbit comments? I can resolve all my comment threads if you use the
/korbit-resolve
command in any comment on your PR.- Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
- Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.
Customizing Korbit
- Check out our docs on how you can make Korbit work best for you and your team.
- Customize Korbit for your organization through the Korbit Console.
Current Korbit Configuration
General Settings
Setting Value Review Schedule Automatic excluding drafts Max Issue Count 10 Automatic PR Descriptions ✅ Issue Categories
Category Enabled Naming ✅ Database Operations ✅ Documentation ✅ Logging ✅ Error Handling ✅ Systems and Environment ✅ Objects and Data Structures ✅ Readability and Maintainability ✅ Asynchronous Processing ✅ Design Patterns ✅ Third-Party Libraries ✅ Performance ✅ Security ✅ Functionality ✅ Feedback and Support
One further item worth noting: Perplexity's currently-supported "online" models charge per request in addition to per token (see https://docs.perplexity.ai/guides/pricing). The model list/pricing files only have price per token fields. Not sure if it's worth a warning or note somewhere, and wasn't sure where the maintainers would want that. |
"litellm_provider": "perplexity", | ||
"mode": "chat" | ||
}, | ||
"perplexity/sonar-medium-chat": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this pr removes pricing. but i see a few new perplexity models - can those be added within this pr? @abromberg
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unless I'm misunderstanding something, my updates bring it in line with the currently supported models:

Those are the three models I left in the pricing files. Is there something else you want me to do?
(I also just added the per-request cost in commit edaa030 on this PR)
Title
Update docs and models files to reflect Perplexity supported models (November 2024)
Relevant issues
Model lists and docs did not reflect Perplexity currently supported models https://docs.perplexity.ai/guides/model-cards
Type
📖 Documentation
Changes
[REQUIRED] Testing
No new tests, no UI changes
Description by Korbit AI
What change is being made?
Update the documentation and model configuration files to reflect the latest supported models by Perplexity as of November 2024, including changes in model names, removal of outdated models, and updated citation return behavior.
Why are these changes being made?
These changes ensure the documentation is accurate and up-to-date with the current offerings by Perplexity, enhancing clarity for end-users and synchronizing the model configurations to reflect only the currently supported models. The update also leverages the default behavior change in citation returns, simplifying model implementation for developers.