This repository was archived by the owner on Jul 22, 2025. It is now read-only.
[Request] Improve Documentation of Usage Tiers to Address User Confusion #132
AidanShipperley
started this conversation in
Ideas
Replies: 2 comments
-
I am Tier 1, but "return_related_questions" and "return_images" work fine in the model "sonar". |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for this post and much appreciated. Will make the changes accordingly. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Request
I’d like to formally ask the maintainers (@shubhang98) to address the unclear documentation of the new Usage Tiers feature introduced with the Sonar and Sonar-Pro models.
Issue
Usage Tiers were added to the Perplexity API this past week and I’m excited to see these parameters move out of private beta. However, the documentation is not clearly communicating parameters restricted to particular usage tiers in the broader API docs. Users are regularly missing the tiered parameter restrictions with the information contained on just one wiki page, resulting in confusion and frustration.
Discussion Post References
Since the release, multiple users have posted about the API being non-functional when they were simply not in the appropriate usage tier:
Users did not know search domain filters were limited to tier 3.
Structured outputs have been assumed to be broken, but users were just not in tier 3.
Returning of related images & related questions were assumed to be broken, but user was not in tier 2.
Proposed Solution
Add relevant parameter tier restrictions to the API Reference page.
Clarify tier requirements in the Structured Outputs Guide.
The API should return an error for unauthorized parameter usage.
Conclusion
Implementing these changes would significantly reduce user confusion and improve the overall experience. New and experienced users alike would benefit from clearer, more consistent documentation—and an error response when they try to use parameters outside their usage tier would make troubleshooting much more straightforward.
Thank you for your time and consideration in resolving these documentation gaps. Please let me know if there is any additional information I can provide to help with these updates.
Beta Was this translation helpful? Give feedback.
All reactions