hermes - 💡(How to fix) Fix Feature request: add iFlow Search as a native Web Search & Extract provider

Summary

I would like to propose adding iFlow Search as a native Hermes Web Search & Extract provider.

This is intentionally different from the existing MCP-based iFlow configuration/docs route. The proposed integration uses Hermes' native web provider abstraction so users can select iFlow directly from the Web Search & Extract provider picker and configure their own IFLOW_API_KEY.

Motivation

Hermes already separates network-related providers by toolset. iFlow Search is not a Browser Automation provider because it does not create browser sessions or expose a CDP URL. It fits the Web Search & Extract provider layer instead:

• webSearch maps to Hermes search
• webFetch maps to Hermes extract/fetch
• imageSearch can remain out of scope for the first version because Hermes does not appear to have a dedicated image-search provider abstraction for this path

The user experience would be:

1. User opens the Web Search & Extract provider selection flow
2. User selects iFlow Search
3. User enters their own IFLOW_API_KEY
4. Hermes uses the default iFlow platform base URL, https://platform.iflow.cn
5. Hermes web search/extract calls use iFlow Search API

Proposed provider

Provider name:

iflow

Display name:

iFlow Search

Suggested UI copy:

iFlow Search [paid] - Search + extract in one provider.

Configuration:

• IFLOW_API_KEY
  • required
  • secret
  • BYOK

Default base URL:

https://platform.iflow.cn

API mapping

iFlow Search API docs:

https://platform.iflow.cn/docs/

Proposed mapping:

Authentication:

Authorization: Bearer <IFLOW_API_KEY>

Out of scope for first version:

• POST /api/search/imageSearch

Local prototype status

I have a local prototype implementation ready for review. It adds a native Web Search & Extract provider, not a Browser Automation provider.

Implemented locally:

• plugins/web/iflow/provider.py
• plugins/web/iflow/plugin.yaml
• plugins/web/iflow/__init__.py
• iFlow env metadata for IFLOW_API_KEY
• iFlow backend allowlist / registry preference wiring
• tests for provider discovery and provider behavior

Validation completed locally:

uv run --extra dev pytest tests/tools/test_web_providers_iflow.py tests/plugins/web/test_web_search_provider_plugins.py
74 passed, 2 deselected

uv run --extra dev ruff check ...
All checks passed

A real BYOK smoke test with IFLOW_API_KEY also passed locally. No API key or Authorization header is included here.

Question

Would the Hermes maintainers be open to a PR adding iFlow Search as a native Web Search & Extract provider?

If yes, I can prepare a focused PR with the local implementation and tests.