Frequently Asked Questions
- The API uses the same search system as the UI with differences in configuration - so their outputs may differ.
- The underlying AI model might differ between the API and the UI for a given query.
- We give users the power to tune the API to their respective use cases using sampling parameters like
presence_penalty
,top_p
etc and custom tuning to specific use cases might lead to less generalization of the API/different results vs the UI. We set optimized defaults and recommend not to explicitly provide sampling parameters in your API requests.
We collect the following types of information:
API Usage Data: We collect billable usage metadata such as the number of requests and tokens. You can view your own usage in the Perplexity API dashboard.
User Account Information: When you create an account with us, we collect your name, email address, and other relevant contact information.
Yes, the Sonar Models, leverage information from Perplexity’s search index and the public internet.
You can find our rate limits here.
We email users about new developments and also post in the changelog.
401 error codes indicate that the provided API key is invalid, deleted or belongs to an account which ran out of credits. You likely need to purchase more credits in the Perplexity API dashboard. You can avoid this issue by configuring auto-top-up.
Currently, we do not support fine-tuning.
Please reach out to api@perplexity.ai or support@perplexity.ai for other API inquiries. You can also post on our discussion forum and we will get back to you.
We do not guarantee this at the moment.
The models are hosted in the US and we do not train on any of your data. And no, your data is not going to China.
Yes, our reasoning APIs that use DeepSeek’s models are uncensored and on par with the other APIs in terms of content moderation.
Yes, you will have access to the model’s CoT.