I gotta say, having white blurry blobs of something in the background floating behind white/grey text maybe wasn't the best design-choice out there.
None the less, I tried to find the actual APIs/service/software used for the "search" part, as I've found that to be the hardest to actually get right (at least for as-local-as-possible usage) for my own "Deep Research Agent".
I've experimented with Brave's search API which worked OK, but seems pricey for agent usage. Currently experimenting with using my own (local) YaCy instance right now, which actually gives me higher quality artifacts at the end, as there are no rate-limits and the model can do hundreds of search calls without me worrying about the cost. But it isn't very quick at picking up some stuff like news and more, otherwise works OK too.
What is the author doing here for the actual searching? Anyone else have any other ideas/approaches to this?
So the core idea is the Deep Orchestrator is pretty unopinionated on what to use for searching, as long as it is exposed over MCP. I tried with a basic fetch server that's one of the reference MCP servers (with a single tool called `fetch`), and also tried with Brave.
I think the folks at Jina wrote some really good stuff on the actual search part: https://jina.ai/news/a-practical-guide-to-implementing-deeps... -- and how to do page/url ranking over the course of the flow. My recommendation would be to do all that in an MCP server itself. That keeps the "deep orchestrator" architecture fairly clean, and you can plug in increasingly sophisticated search techniques over time.
Self host an instance of SearXNG[1] either locally or on a remote server with a simple docker container and use its JSON API [2]. You have to enable the JSON API in the config manually [3].
I'm using mcp-agent and have tried the orchestrator workflow pattern[0]. For deep research I'm having mixed results. As far as I can tell, it's not using prompt caching[1] with Anthropic models, nor the gpt-5 responses API[2], which is preferable to the completions API. The many MCP tools from a handful of servers eat up a lot of context. It doesn't report progress, so it'll just spin for minutes at a time without meaningful indication. Mostly it has been high cost and high latency without great grounding in source facts. I like the interface overall, but some of the patterns and examples were convoluted. I'm aware that mcp-agent is being worked on, and I look forward to improvements.
OP here -- I think the general principle I would recommend is using a big reasoning model for the planning phase. I think Claude Code and other agents do the same. The reason this is important is because the quality of the plan really affects the final result, and error rates will compound if the plan isn't good.
based on the article, it seems like a good reasoning model like gpt5 or opus 4.1 might be good choices for the planner. I wonder if the gpt oss reasoning models would do well
diggan|5 months ago
None the less, I tried to find the actual APIs/service/software used for the "search" part, as I've found that to be the hardest to actually get right (at least for as-local-as-possible usage) for my own "Deep Research Agent".
I've experimented with Brave's search API which worked OK, but seems pricey for agent usage. Currently experimenting with using my own (local) YaCy instance right now, which actually gives me higher quality artifacts at the end, as there are no rate-limits and the model can do hundreds of search calls without me worrying about the cost. But it isn't very quick at picking up some stuff like news and more, otherwise works OK too.
What is the author doing here for the actual searching? Anyone else have any other ideas/approaches to this?
saqadri|5 months ago
So the core idea is the Deep Orchestrator is pretty unopinionated on what to use for searching, as long as it is exposed over MCP. I tried with a basic fetch server that's one of the reference MCP servers (with a single tool called `fetch`), and also tried with Brave.
I think the folks at Jina wrote some really good stuff on the actual search part: https://jina.ai/news/a-practical-guide-to-implementing-deeps... -- and how to do page/url ranking over the course of the flow. My recommendation would be to do all that in an MCP server itself. That keeps the "deep orchestrator" architecture fairly clean, and you can plug in increasingly sophisticated search techniques over time.
Zetaphor|5 months ago
[1] https://docs.searxng.org/admin/installation-docker.html#inst...
[2] https://docs.searxng.org/dev/search_api.html
[3] https://github.com/searxng/searxng/discussions/3542
mbil|5 months ago
[0]: https://docs.mcp-agent.com/workflows/orchestrator
[1]: https://docs.anthropic.com/en/docs/build-with-claude/prompt-...
[2]: https://platform.openai.com/docs/guides/migrate-to-responses
ilovefood|5 months ago
asail77|5 months ago
saqadri|5 months ago
haniehz|5 months ago