9router-web-search
- Repo stars 16,108
- Author updated Live
- Author repo 9router
- Domain
- Writing
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @decolua · no license declared
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Env read
- Write / modify
- Network behavior
- External requests
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: 9router-web-search
description: Web search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / L…
category: writing
runtime: no special runtime
---
# 9router-web-search output preview
## PART A: Task fit
- Use case: Web search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity. Use when the user wants to search the web, look up information, find articles, or query a search engine..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Discover / Endpoint / Examples” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Web search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / You.com / Perplexity. Use when the user wants to search the web, look up information, find articles, or query a search engine.”.
- **02** When the source has headings, the agent prioritizes “Discover / Endpoint / Examples” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, read environment variables, write/modify files; may access external network resources; usually needs no extra API key.
## Running Rules
- read files, read environment variables, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/search`, `/v1`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, read environment variables, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Discover / Endpoint / Examples”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: 9router-web-search
description: Web search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / L…
category: writing
source: decolua/9router
---
# 9router-web-search
## When to use
- Web search via 9Router /v1/search using Tavily / Exa / Brave / Serper / SearXNG / Google PSE / Linkup / SearchAPI / Yo…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Discover / Endpoint / Examples” and keep inference separate from source facts.
- read files, read environment variables, write/modify files; may access external network resources; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "9router-web-search" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Discover / Endpoint / Examples
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, read environment variables, write/modify files | may access external network resources
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}9Router — Web Search
Requires NINEROUTER_URL (and NINEROUTER_KEY if auth enabled). See https://raw.githubusercontent.com/decolua/9router/refs/heads/master/skills/9router/SKILL.md for setup.
Discover
curl $NINEROUTER_URL/v1/models/web | jq '.data[] | select(.kind=="webSearch") | .id'
# Per-provider params (searchTypes, maxResults, required options like cx for google-pse)
curl "$NINEROUTER_URL/v1/models/info?id=tavily/search"IDs end in /search (e.g. tavily/search). Combos (owned_by:"combo") chain providers with auto-fallback.
Endpoint
POST $NINEROUTER_URL/v1/search
| Field | Required | Notes |
|---|---|---|
model (or provider) |
yes | from /v1/models/web (e.g. tavily or brave) |
query |
yes | search query |
max_results |
no | default 5 |
search_type |
no | web (default) / news |
country, language, time_range, domain_filter |
no | provider-dependent |
Examples
curl -X POST $NINEROUTER_URL/v1/search \
-H "Authorization: Bearer $NINEROUTER_KEY" \
-H "Content-Type: application/json" \
-d '{"model":"tavily","query":"9Router open source","max_results":5}'JS:
const r = await fetch(`${process.env.NINEROUTER_URL}/v1/search`, {
method: "POST",
headers: { "Authorization": `Bearer ${process.env.NINEROUTER_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({ model: "search-combo", query: "latest LLM benchmarks", max_results: 10 }),
});
console.log(await r.json());Response shape
{
"provider": "tavily",
"query": "9Router open source",
"results": [
{
"title": "...", "url": "https://...", "display_url": "github.com/...",
"snippet": "...", "position": 1, "score": 0.92,
"published_at": null, "favicon_url": null, "content": null,
"metadata": { "author": null, "language": null, "source_type": null, "image_url": null },
"citation": { "provider": "tavily", "retrieved_at": "2026-...", "rank": 1 }
}
],
"answer": null,
"usage": { "queries_used": 1, "search_cost_usd": 0.008 },
"metrics": { "response_time_ms": 850, "upstream_latency_ms": 700, "total_results_available": 12 },
"errors": []
}Provider quirks
All accept query + max_results. Optional fields vary:
| Provider | Supports | Required extras |
|---|---|---|
tavily |
country, domain_filter, news topic | — |
exa |
domain_filter (incl/excl), news category | — |
brave-search |
country, language | — |
serper |
country, language, news endpoint | — |
perplexity |
country, language, domain_filter | — |
linkup |
domain_filter, time_range | depth: fast/standard/deep (option) |
google-pse |
country, language, time_range, offset | cx required (providerOptions) |
searchapi |
country, language, pagination | — |
youcom |
country, language, time_range, domain_filter, full_page | — |
searxng |
language, time_range | Self-hosted, noAuth |
Provider IS the model — "provider":"tavily" ≡ "model":"tavily".
Decide Fit First
Design Intent
How To Use It
Boundaries And Review