Spy Search is an agentic search framework designed to outperform current web search agents with a focus on faster, more efficient daily usage.
While commercial solutions like Manus charge $200 per month, Spy Search leverages open-source models to provide a cost-effective alternative without sacrificing performance. Currently our searching-speed is quite slow yet we can generate a long length consistent report (around 2000 words) with latest current information! This problem will be tackle after the release of v1.0.
News: 2025-06-10 Spy-searcher has just released v0.3 !
First you have to clone the repo
git clone https://github.com/JasonHonKL/spy-search.git
cd spy-search
To set up just run
python setup.py
Add your API key in the .env file if you want to use API. Currently we support openAI, Claude, Gork & Deepseek. If you use ollama you don't need to do anything.
config the config.json file, you may copy the following template
{
"provider": "openai",
"model": "",
"agents": [
"reporter",
"searcher"
],
"db": "./local_files/test",
"base_url": "https://openrouter.ai/api/v1"
}
After that run (due to some problem some computers espically using ollama may have some issue) If you are a developer we strongly suggest you follow the guide from contributing .md which is much more convience.
docker build -t spy-searcher .
docker run -p 8000:8000 -p 8080:8080 -e OLLAMA_HOST=host.docker.internal spy-searcher
Now you can access
http://localhost:8000
Watch the demo video on YouTube:
Screen.Recording.2025-06-14.at.12.45.52.AM.MOV
We welcome contributions from the community! Here’s how you can contribute:
- We appreciate pull requests that fix bugs, add features, or improve documentation.
- Please ensure your PR:
- Is based on the latest
main
branch. - Includes clear descriptions and testing instructions.
- Passes all automated tests and checks.
- Is based on the latest
Once submitted, maintainers will review your PR and provide feedback or merge it if it meets the project standards.
- Feel free to open issues for bugs, feature requests, or questions.
- When submitting an issue, please include:
- A clear and descriptive title.
- Steps to reproduce (for bugs).
- Expected and actual behavior.
- Any relevant environment or version information.
Maintainers will acknowledge your issue, label it appropriately, and work on resolving it or discuss it with you.
Thank you for helping improve this project! Your contributions make a difference.