Search Fusion

Federated web search for OpenClaw.

This plugin reuses the web search providers you already have configured, fans them out in parallel, merges duplicate URLs, preserves which provider found what, and keeps the raw evidence attached.

Requirements

• OpenClaw 2026.3.22 or newer

The broker relies on the newer plugin runtime web-search helpers. Older OpenClaw builds may install the package but will not provide the runtime surface this plugin expects.

What it adds

• A web search provider named search-fusion
• A direct agent tool named search_fusion
• A helper tool named search_fusion_providers
• A provider capability taxonomy in src/provider-capabilities.ts

Why this exists

OpenClaw already has solid search providers. The missing piece was orchestration.

Search Fusion is the orchestration layer:

• discover configured providers
• run them in parallel
• retry transient provider failures with configurable policy
• merge duplicate URLs
• keep provider attribution intact
• preserve raw provider payloads and per-provider merged variants
• expose native ranks, deterministic flags, merged rankings, and machine-readable ranking explainability
• emit structured payload.evidenceTable rows for downstream evidence-table renderers (for example Atlas)
• expose one clean result set back to the agent

Install

Search Fusion is a native OpenClaw code plugin, so ClawHub labeling it as Code Plugin is correct.

# recommended: ClawHub first, npm fallback
openclaw plugins install @vacinc/search-fusion

# explicit ClawHub-only install
openclaw plugins install clawhub:@vacinc/search-fusion

Configure

Optional plugin config:

{
  "plugins": {
    "entries": {
      "search-fusion": {
        "enabled": true,
        "config": {
          "modes": {
            "fast": ["brave"],
            "balanced": ["brave", "tavily"],
            "deep": ["brave", "tavily", "gemini", "minimax"],
            "coding": ["minimax", "brave"],
            "cheap": ["duckduckgo", "brave"],
            "results": ["brave", "duckduckgo", "minimax"],
            "answers": ["gemini"]
          },
          "intentProviders": {
            "research": ["gemini", "tavily", "brave", "minimax"],
            "keyword":  ["brave", "duckduckgo", "minimax"],
            "answer":   ["gemini"],
            "news":     ["brave", "tavily"],
            "local":    ["brave"]
          },
          "defaultMode": "balanced",
          "excludeProviders": ["grok"],
          "sourceTierMode": "balanced",
          "countPerProvider": 5,
          "maxMergedResults": 10,
          "providerTimeoutMs": 15000,
          "retry": {
            "maxAttempts": 3,
            "backoffMs": 750,
            "backoffMultiplier": 2,
            "maxBackoffMs": 5000
          },
          "providerConfig": {
            "gemini": {
              "timeoutMs": 60000,
              "weight": 1.3,
              "retry": {
                "maxAttempts": 4,
                "backoffMs": 1500
              }
            },
            "duckduckgo": {
              "weight": 0.8
            }
          }
        }
      }
    }
  }
}

If modes is omitted, Search Fusion auto-generates starter modes from discovered providers:

• fast → first configured provider (or first available provider if nothing is configured)
• balanced → first two configured providers (or first two available)
• deep → all configured providers (or all available)

If you set modes, your map is treated as authoritative and replaces those starter defaults.

Resolution order:

• explicit providers
• explicit mode (from custom modes, or starter modes when custom modes are absent)
• intent hint → matched against intentProviders map
• configured defaultMode
• configured defaultProviders (backward compatibility)
• otherwise all configured providers

providerConfig.<id> is the canonical place for per-provider overrides like retry, timeoutMs, count, and weight.

providerConfig.<id>.weight is a ranking multiplier (default 1, range 0.1 to 5). Higher values boost trusted providers, lower values down-weight noisier ones.

sourceTierMode controls deterministic trust-tier downranking:

• off: disables source-tier adjustments
• balanced (default): favors high-trust result classes and downranks low-trust classes
• strict: stronger suppression of lower-trust classes

Intent-based routing

Set intentProviders to bias provider selection when a caller passes an intent hint. The intent is applied after explicit providers/mode but before defaultMode/defaultProviders, so it only kicks in when the caller leaves routing unspecified.

Supported intents:

Intent	Suggested use	Example providers
research	In-depth investigation; prefers answer/grounding plus a strong technical-results provider	gemini, tavily, brave, minimax
keyword	Classic keyword/web search	brave, duckduckgo, minimax
answer	Direct answer expected	gemini, perplexity, grok
news	Recent news / current events	brave, tavily
local	Location-aware queries	brave

Example config snippet:

{
  "plugins": {
    "entries": {
      "search-fusion": {
        "config": {
          "intentProviders": {
            "research": ["gemini", "tavily", "brave", "minimax"],
            "keyword":  ["brave", "duckduckgo", "minimax"],
            "answer":   ["gemini", "perplexity"],
            "news":     ["brave", "tavily"],
            "local":    ["brave"]
          }
        }
      }
    }
  }
}

When intentProviders has no entry for the given intent, or the mapped providers are unavailable, routing falls through to defaultMode, defaultProviders, and finally all configured providers.

If you want the built-in web_search tool to route through the broker by default:

{
  "tools": {
    "web": {
      "search": {
        "provider": "search-fusion"
      }
    }
  }
}

Tool usage

search_fusion

Example prompt:

• Search across all configured providers for openclaw plugin sdk runtime helpers
• Search brave and tavily only for best local llm web search api with 3 results each
• Search in deep mode for best local llm web search api

Supported arguments:

• query
• intent — optional routing hint: research, keyword, answer, news, or local
• mode — mode name from configured modes, or starter modes (fast, balanced, deep) when custom modes are not set
• providers — provider ids, or all
• count
• maxMergedResults
• country
• language
• freshness
• date_after
• date_before
• search_lang
• ui_lang
• includeFailures

Ranking explainability

Merged payloads include:

• results[].ranking with the final rank, score breakdown (bestVariantScore, corroborationBonus, bestRankBonus, tierAdjustment, flagPenalty, finalScore), and tie-breaker values.
• top-level ranking metadata with the strategy, sort order, considered/returned counts, and dropped[] entries (with reason: "maxMergedResults") for results trimmed by the output cap.

search_fusion_providers

Lists the providers visible to the broker and whether they appear configured.

Evidence table output (payload.evidenceTable)

Search Fusion emits a table-ready structure for downstream consumers like Atlas.

• columns[] provides stable column metadata (key, label, description)
• rows[] has one row per merged URL (rowId is the canonical URL)
• rows[].answerCitationSupport tracks citation count and citing providers from answer-style runs
• rows[].providerEvidence[] keeps provider-level rank, score, source type, flags, and snippets for drill-down cells

Example flattening transform:

const tableRows = payload.evidenceTable.rows.map((row) => ({
  rank: row.rank,
  title: row.title,
  url: row.url,
  providers: row.providers.join(", "),
  providerCount: row.providerCount,
  bestRank: row.bestRank,
  score: Number(row.score.toFixed(3)),
  answerCitationCount: row.answerCitationSupport.count,
  flags: row.flags.join(", "),
}));

Development

pnpm install
pnpm check
pnpm test

Current behavior

• starter modes are built in for fresh installs (fast, balanced, deep) when modes is not configured
• custom modes are authoritative and replace the starter map
• falls back to all configured providers when nothing else is specified
• treats keyless providers (for example DuckDuckGo) as configured/available
• excludes itself to avoid recursion
• dedupes by canonical URL
• retries transient provider failures with global defaults and per-provider overrides via providerConfig.<id>.retry
• supports deterministic provider weighting via providerConfig.<id>.weight to bias ranking by provider trust/value
• isolates unexpected provider pipeline crashes so one provider cannot abort the whole fusion run
• preserves raw provider payloads in providerRuns[]
• preserves per-provider merged variants in results[].variants[]
• emits evidenceTable.columns[] and evidenceTable.rows[] for direct evidence-table rendering
• includes evidenceTable.rows[].answerCitationSupport and providerEvidence[] helper fields for claim-support views
• surfaces deterministic flags like sponsored, redirect-wrapper, tracking-stripped, community, and video
• surfaces native ranks, merged rankings, per-result score breakdowns, and dropped-result reasons so ranking decisions are auditable
• classifies each hit into a source tier (high, standard, low, suppressed) and downranks lower-trust classes deterministically
• carries answer-style providers (Gemini / Grok / Kimi / Perplexity) as provider digests with fullContent, citation details, and citation-derived hits
• supports intent routing hints (research, keyword, answer, news, local) that bias provider selection without overriding explicit providers or mode

Provider capability taxonomy

Each provider carries a set of declarative capability tags that describe what it is good at. These are resolved at discovery time and attached to ResolvedProvider.capabilities.

import {
  resolveProviderCapabilities,
  hasCapability,
  filterByCapabilities,
  filterByAnyCapability,
  ALL_PROVIDER_CAPABILITIES,
} from "@vacinc/search-fusion";

// What can brave do?
resolveProviderCapabilities("brave");      // ["news", "privacy", "results"]
resolveProviderCapabilities("gemini");     // ["answer", "results"]
resolveProviderCapabilities("exa");        // ["academic", "code", "neural", "results"]
resolveProviderCapabilities("duckduckgo"); // ["free-tier", "privacy", "results"]
resolveProviderCapabilities("minimax");    // ["code", "results"]

// Does tavily synthesise answers?
hasCapability(resolveProviderCapabilities("tavily"), "answer"); // true

// Which providers are both neural and answer-capable?
filterByCapabilities(["brave", "exa", "tavily", "perplexity"], ["neural", "answer"]);
// => ["tavily", "perplexity"]

// Which providers have any privacy-preserving capability?
filterByAnyCapability(["brave", "duckduckgo", "gemini"], ["privacy", "free-tier"]);
// => ["brave", "duckduckgo"]

Full capability vocabulary

Tag	Meaning
results	Returns a ranked list of URLs/snippets (classic web search).
answer	Synthesises a grounded prose answer alongside or instead of links.
news	Has a dedicated news index or strong freshness/recency signal.
images	Can return image results.
video	Can return video results.
local	Strong local / maps intent handling.
academic	Indexed academic or scientific content.
code	Particularly good at code / technical queries.
neural	Uses neural / semantic retrieval rather than (only) keyword matching.
free-tier	Usable at meaningful call volume without a paid API key.
privacy	Explicitly avoids user-level tracking.

Known registry (built-in)

Provider id	Capabilities
brave	news, privacy, results
duckduckgo	free-tier, privacy, results
exa	academic, code, neural, results
gemini	answer, results
google	images, local, news, results, video
grok	answer, news, results
kimi	answer, results
minimax	code, results
perplexity	answer, neural, results
searxng	free-tier, privacy, results
serper	images, local, news, results, video
tavily	answer, neural, results

Providers not in the registry return an empty capability set (treated as general-purpose). Future routing features such as cost-aware mode selection and automatic mode generation will build on this taxonomy.

Next upgrades

• capability-driven automatic mode generation (e.g. auto-select answer providers for question-style queries)
• provider weighting based on capability scores
• cost-aware routing modes
• caching at the broker layer
• optional fetch/expansion of top merged hits