OpenCode
Give OpenCode live web search, agentic search, news, page retrieval, sitemap discovery, and trending topics with the native opencode-search1api plugin.
opencode-search1api is a native OpenCode plugin that gives the agent live web access through Search1API — web search, agentic search, news search, readable page retrieval, sitemap discovery, and trending topics.
Unlike an MCP bridge, the plugin registers these as first-class OpenCode tools.
Install
Install for the current project:
opencode plugin opencode-search1apiOr install globally:
opencode plugin opencode-search1api --globalAuthentication
Use one of these methods:
- Set
SEARCH1API_KEYin the OpenCode environment. - Install
search1api-cliand runs1 loginonce; the plugin reuses the same OAuth session. - Pass an
apiKeyinopencode.json:
{
"plugin": [
["opencode-search1api", { "apiKey": "your-api-key" }]
]
}Prefer an environment variable or secret manager over committing credentials. Create a key in the Search1API dashboard if you need one.
What the agent can do
| Tool | What it does |
|---|---|
search1api_search | Live web search |
search1api_ask | Agentic search with only query (five credits, 45-second timeout) |
search1api_news | News search |
search1api_crawl | Read a public URL as clean Markdown |
search1api_sitemap | Enumerate a site's URLs |
search1api_trending | Trending GitHub repos or Hacker News stories |
search1api_ask accepts only query (1-500 characters). Its response preserves
query, intent, result source and relevance, and optional errors.
See Ask.
Credits
Search and news requests cost one credit each; crawling a page costs one additional credit per successfully crawled page. Agentic search costs five credits per request. New accounts receive 100 credits without a credit card. See Credits and limits for current rates.
Search filters and result fields
Version 0.2.0 supports all 19 search engines and all six
news sources, including Bing China, Yandex, Grokipedia, and Reuters.
time_range supports day, week, month, and year; page supports search
pagination. These filters apply to search/news; agentic search accepts only query.
Engine-specific result fields live in optional metadata: GitHub search exposes
metadata.kind, metadata.stars, metadata.language, and metadata.num_comments;
Hacker News search exposes metadata.story_url, metadata.points, and
metadata.num_comments. Optional published_date stays at the result top level.
The response-level searchParameters describes the executed request. These paths
apply to search/news; trending keeps its separate response shape.