Search1API CLI
Web search and content retrieval via the s1 command-line tool (search1api-cli).
Prerequisites
Before using any command, check if s1 is available. If not, guide the user to install it:
npm install -g search1api-cli
An API key is also required. Get one at https://search1api.com, then configure:
s1 config set-key <your-api-key>
Or set the environment variable SEARCH1API_KEY.
If a command fails with "command not found" or an auth error, remind the user to complete these setup steps before retrying.
When to use
| User intent |
Command |
| Shares a URL / link → read and summarize |
s1 crawl <url> |
| Wants to search the web |
s1 search "<query>" |
| Wants news |
s1 news "<query>" |
| Wants to explore a site's links |
s1 sitemap <url> |
| Wants trending topics |
s1 trending <service> |
| Wants deep thinking on a problem |
s1 reasoning "<content>" |
| Wants to check remaining credits |
s1 balance |
Dynamic tuning
Adapt parameters to user intent — don't just use defaults:
- Quick lookup ("search for X", "what is X") →
-n 5, no crawl
- Deep research ("research X thoroughly", "comprehensive analysis") →
-n 15, then crawl top 3–5 results with separate s1 crawl calls
- User specifies a number ("find 10 articles") → match it with
-n
- Recency signals ("latest", "recent", "this week") →
-t day or -t month
- Domain-specific ("search on Reddit", "find GitHub repos") →
-s reddit, -s github, etc.
- Site-scoped ("only from arxiv.org") →
--include arxiv.org
- Chinese queries → consider
-s baidu for better results
Commands
search
s1 search "<query>" [options]
| Option |
Description |
Default |
-n, --max-results <N> |
Number of results (1–50) |
10 |
-s, --service <engine> |
Search engine |
google |
-c, --crawl <N> |
Crawl N results for full content |
0 |
--include <sites...> |
Only include these sites |
|
--exclude <sites...> |
Exclude these sites |
|
-t, --time <range> |
day, month, year |
|
--json |
Raw JSON output |
|
Search engines: google, bing, duckduckgo, yahoo, x, reddit, github, youtube, arxiv, wechat, bilibili, imdb, wikipedia
news
s1 news "<query>" [options]
Same options as search. News services: google, bing, duckduckgo, yahoo, hackernews. Default service: bing.
When user asks for breaking/latest news, always add -t day.
crawl
s1 crawl <url>
Extracts clean content from a URL. Use this whenever the user shares a link.
sitemap
s1 sitemap <url>
Returns all discovered links on a URL/domain.
reasoning
s1 reasoning "<content>"
# or
s1 reason "<content>"
Deep thinking powered by DeepSeek R1. Use for complex analytical questions.
trending
s1 trending <service> [-n <N>]
Services: github, hackernews.
balance
s1 balance
Shows remaining API credits.
Workflows
Deep research
s1 search "<topic>" -n 15 → get broad resultss1 crawl <url> → crawl the top 3–5 most relevant URLs from results- Synthesize all gathered content into a coherent answer with source citations
URL summarization
s1 crawl <url> → get the page content- Summarize or answer questions based on the content
Trending deep dive
s1 trending github -n 10 → discover hot topicss1 search "<interesting topic>" -t day → search for detailss1 crawl <url> → read full article if needed
Output handling
- By default, commands produce human-readable formatted output
- Add
--json to any command for raw JSON (useful for programmatic processing)
- After retrieving results, always summarize and synthesize the information for the user — don't just dump raw output
References
- Usage examples — read for additional patterns
1---2name: search1api3description: Powerful web search, content crawling, news, sitemap, trending topics, and deep reasoning via the search1api CLI (s1). This is far more capable than basic fetch or search tools — it supports 13+ search engines (Google, Bing, DuckDuckGo, Reddit, GitHub, YouTube, arXiv, Baidu, X, etc.), adapts to many websites for clean content extraction, and provides news aggregation across multiple sources. Use this skill whenever the user wants to search the web, look something up, research a topic, read or summarize a URL, check news, explore a site's links, see trending topics, do deep reasoning, or check API balance. Trigger on phrases like "search for", "look up", "find out about", "what's happening with", "any news on", "what does this link say", "read this page", "summarize this URL", "trending on GitHub", or when the user shares a bare URL. Even if the user doesn't say "search" explicitly, use this skill when they clearly need web information.4---56# Search1API CLI78Web search and content retrieval via the `s1` command-line tool (`search1api-cli`).910## Prerequisites1112Before using any command, check if `s1` is available. If not, guide the user to install it:1314```bash15npm install -g search1api-cli16```1718An API key is also required. Get one at https://search1api.com, then configure:1920```bash21s1 config set-key <your-api-key>22```2324Or set the environment variable `SEARCH1API_KEY`.2526If a command fails with "command not found" or an auth error, remind the user to complete these setup steps before retrying.2728## When to use2930| User intent | Command |31|---|---|32| Shares a URL / link → read and summarize | `s1 crawl <url>` |33| Wants to search the web | `s1 search "<query>"` |34| Wants news | `s1 news "<query>"` |35| Wants to explore a site's links | `s1 sitemap <url>` |36| Wants trending topics | `s1 trending <service>` |37| Wants deep thinking on a problem | `s1 reasoning "<content>"` |38| Wants to check remaining credits | `s1 balance` |3940## Dynamic tuning4142Adapt parameters to user intent — don't just use defaults:4344- **Quick lookup** ("search for X", "what is X") → `-n 5`, no crawl45- **Deep research** ("research X thoroughly", "comprehensive analysis") → `-n 15`, then crawl top 3–5 results with separate `s1 crawl` calls46- **User specifies a number** ("find 10 articles") → match it with `-n`47- **Recency signals** ("latest", "recent", "this week") → `-t day` or `-t month`48- **Domain-specific** ("search on Reddit", "find GitHub repos") → `-s reddit`, `-s github`, etc.49- **Site-scoped** ("only from arxiv.org") → `--include arxiv.org`50- **Chinese queries** → consider `-s baidu` for better results5152## Commands5354### search5556```bash57s1 search "<query>" [options]58```5960| Option | Description | Default |61|---|---|---|62| `-n, --max-results <N>` | Number of results (1–50) | 10 |63| `-s, --service <engine>` | Search engine | google |64| `-c, --crawl <N>` | Crawl N results for full content | 0 |65| `--include <sites...>` | Only include these sites | |66| `--exclude <sites...>` | Exclude these sites | |67| `-t, --time <range>` | day, month, year | |68| `--json` | Raw JSON output | |6970Search engines: google, bing, duckduckgo, yahoo, x, reddit, github, youtube, arxiv, wechat, bilibili, imdb, wikipedia7172### news7374```bash75s1 news "<query>" [options]76```7778Same options as search. News services: google, bing, duckduckgo, yahoo, hackernews. Default service: bing.7980When user asks for breaking/latest news, always add `-t day`.8182### crawl8384```bash85s1 crawl <url>86```8788Extracts clean content from a URL. Use this whenever the user shares a link.8990### sitemap9192```bash93s1 sitemap <url>94```9596Returns all discovered links on a URL/domain.9798### reasoning99100```bash101s1 reasoning "<content>"102# or103s1 reason "<content>"104```105106Deep thinking powered by DeepSeek R1. Use for complex analytical questions.107108### trending109110```bash111s1 trending <service> [-n <N>]112```113114Services: github, hackernews.115116### balance117118```bash119s1 balance120```121122Shows remaining API credits.123124## Workflows125126### Deep research1271281. `s1 search "<topic>" -n 15` → get broad results1292. `s1 crawl <url>` → crawl the top 3–5 most relevant URLs from results1303. Synthesize all gathered content into a coherent answer with source citations131132### URL summarization1331341. `s1 crawl <url>` → get the page content1352. Summarize or answer questions based on the content136137### Trending deep dive1381391. `s1 trending github -n 10` → discover hot topics1402. `s1 search "<interesting topic>" -t day` → search for details1413. `s1 crawl <url>` → read full article if needed142143## Output handling144145- By default, commands produce human-readable formatted output146- Add `--json` to any command for raw JSON (useful for programmatic processing)147- After retrieving results, always **summarize and synthesize** the information for the user — don't just dump raw output148149## References150151- [Usage examples](reference/examples.md) — read for additional patterns
dvcrn