Update docs and models files to reflect Perplexity supported models (November 2024) #6888
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… of november 2024
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
![korbit-ai[bot]](https://avatars.githubusercontent.com/in/322216?s=60&v=4){kind=small}
There was a problem hiding this comment.
I've completed my review and didn't find any issues... but I did find this rooster.
\\
(o>
\\_//)
\_/_)
_|_
Need a new review? Comment
/korbit-reviewon 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-reviewcommand in a comment at the root of your PR.- You can ask Korbit to generate a new PR description using the
/korbit-generate-pr-descriptioncommand in any comment on your PR.- Too many Korbit comments? I can resolve all my comment threads if you use the
/korbit-resolvecommand 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. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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.