Replies: 6 comments 1 reply
-
Having the exact same issue |
Beta Was this translation helpful? Give feedback.
-
The difference between the two is wild. In fact the API based provides such a low quality compared to the web ui it's barely usable. Any help from perplexity would be appreciated. |
Beta Was this translation helpful? Give feedback.
-
We have been getting a lot of similar feedback regarding the deep research model lately. In this case, this doesn't have to do with the differences in configuration between the Web UI and the API. This is one of our top priorities, we expect to make significant progress very soon on this and apologize for any inconvenience caused. |
Beta Was this translation helpful? Give feedback.
-
Yeah I'm in the same boat. API deep research is falling well short of what we need it for. |
Beta Was this translation helpful? Give feedback.
-
Hey @moog500nl @ianrothmann - this is a known issue to us at this time, specifically for the deep research model. We are looking into it and will keep you updated. |
Beta Was this translation helpful? Give feedback.
-
Same problem here. Very poor response from the API compared to the web UI. Hope for a fix soon. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
Significant differences exist between the API output for sonar-deep-research and the web UI. I've tested using EXACTLY the same query for each one, and the API consistently returns a fraction of the cited URLs than the web UI. In my specific example - c.15 (API) vs c.55. Has anyone else spotted this? I saw another thread which mentioned that people were seeing similar results for sonar-pro using a web search and Perplexity gave the feedback that it was because the default system prompt for the web UI is not being inherited via the API and that they would be providing additional tips soon. I'm very curious. Many thanks.
Beta Was this translation helpful? Give feedback.
All reactions