Skip to main content

SearcherKit is a modular system for building AI agents that rely heavily on search. It handles everything from agent rollouts, LLM backends, tool calls, and benchmark evaluation, to training pipelines — all in one project.

What it does

  • Build and run search agents – Define agent behavior once, then use it for prototyping, evaluation, interactive demos, and large‑scale post training.
  • Connect to any data source – Plug in web APIs, Elasticsearch, internal knowledge bases, or local files through a unified interface. Combine sources freely without touching agent code.
  • Scale without pain – Async execution, flexible concurrency, checkpoint recovery, and detailed traces make batch jobs fast and debuggable. Swap models and backends easily.
  • Training‑ready – The same agent and tool configuration can be used for evaluation, offline analysis, and integration with training pipelines, without needing to refactor code.

Why SearcherKit?

  • 🧩 One codebase, many uses – No more copying logic between research and production. What you build for an experiment works directly for evaluation and deployment.
  • 🔌 Plug‑and‑play sources – Add or remove search backends in minutes. The agent doesn’t care where the data comes from.
  • ⚡ Fast and reliable – Native async, smart concurrency, and automatic checkpointing let you run weeks‑long experiments without babysitting.
  • 🏆 Proven in RL – We’ve used it to train competitive 8B models on real search tasks. The same pipeline is open and ready for your own training.

🚀 Quick Start

Jump right in with the Quick Start guide — you’ll have a search agent running in minutes.

📖 Documentation

Browse the docs by topic:


🤝 Contributing

SearcherKit is under active development. We welcome issues and pull requests for reproduction reports, new model parsers, source adapters, benchmark recipes, training integrations, bug fixes, documentation, and more.

If SearcherKit helps your research or simplifies your agent stack, please give us a ⭐ on GitHub – it helps others discover the project.

👤 The Team

SearcherKit is built and maintained by the group of Assistant Professor Wei Hongxin and Professor Jing Bingyi in SUSTech and CUHK-SZ.
Core maintainers: Li Hanyang, Zhang Haotian, Yang Hanjie, Wang Shuoyuan, Chen Yiyang, Lan Zijie, and Yu Zhengye.

📜 License

SearcherKit is licensed under the MIT License.

Metadata

Release files for searcherkit 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for searcherkit 0.1.1
File Size Uploaded
searcherkit-0.1.1.tar.gz 3.0 MB Details

Built distribution (wheel)

Table of built distributions (wheels) for searcherkit 0.1.1
File Interpreter ABI Platform
searcherkit-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 3.3 MB

Release files / searcherkit-0.1.1.tar.gz

Download URL searcherkit-0.1.1.tar.gz
Size 3.0 MB
Tags Source
SHA-256 checksum
How to use checksums
9a7eda8c15f335ebdb9ea725cba496ae14180e449dda72611490ddf70ce44c03
BLAKE2b-256 checksum
How to use checksums
198330f48afdb2c2a9189bd15495cd0a859101750080ac0f538fef25936d8081
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.

Transparency log

Release files / searcherkit-0.1.1-py3-none-any.whl

Download URL searcherkit-0.1.1-py3-none-any.whl
Size 218.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7da6fddfe59d75071b41ceccaacb7a8893b84451f53bc04956d16925002283b9
BLAKE2b-256 checksum
How to use checksums
1e1fa09f7385ad7af17855a53c4b4451d60025390a2eb39782f0761239765c93
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Jul 20, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page