Conversation
|
Hey @kncshw Thanks for contributing! One thing I'm a bit hesitant about: since Firecrawl just returns raw scraped content (unlike Perplexity which does search + LLM summary in one go), this implementation ends up making a separate LLM call inside the tool to synthesize the results. That feels a bit awkward architecturally - "tools" shouldn't really be calling LLMs on their own, and it adds a fair amount of complexity. Do you think we could simplify by just returning the raw Firecrawl markdown and letting the agent handle it? Or maybe just use another search API with a free tier (like Exa.ai, etc) that works more like Perplexity out of the box? |
|
Yes, your concern is valid. I think this: 'Do you think we could simplify by just returning the raw Firecrawl markdown and letting the agent handle it? ' could be a better option. thanks. |
Purpose for this enhancement:
Test has been completed with Firecrawl but I have not tested the Perplexity as I do not have the API key. The Maintainer needs to do regression tests with Perplexity API key