querit-plugins

Official Querit search integrations for automation and AI agent platforms.

Querit delivers real-time, authoritative web search results and clean page content for LLM applications. Each integration in this repository connects one platform to the Querit API (/v1/search + /v1/contents) for live web search and page fetching — with cited sources, domain/region/language/time-range filters, and output that is always treated as untrusted web data. The Oh My Pi entry below documents an upstream built-in provider, not a package in this repository.

Two more integrations live in this repository but are not generally available yet:

How each package integration reads the API key and search defaults is covered in its own section below; the Oh My Pi section documents its upstream built-in provider.

Get an API key

Sign up on Querit.ai to get an API key with 1,000 free API calls per month — no credit card required. The same key works for all integrations.

querit — Oh My Pi (OMP)

The pending upstream OMP change adds a built-in Querit provider for both its web_search provider chain and the URL-fetch/reader path used by the built-in read tool. This is not an npm plugin from this repository, so there is nothing to install here. Available after the upstream PR is merged.

Credentials

• Set QUERIT_API_KEY in the environment that launches OMP, or
• run /login querit in OMP and paste/save the key when prompted.

Select Querit

After the upstream PR is merged, make Querit the first web_search provider and select it for URL fetching with:

omp config set providers.webSearchOrder '["querit"]'
omp config set providers.fetch querit

providers.webSearchOrder controls web_search provider priority, while providers.fetch controls the reader backend used when OMP's read tool fetches an HTTP(S) URL. After the upstream change lands, its search provider will send requests to POST https://api.querit.ai/v1/search with only { query, count } (count defaults to 10 and is clamped to 1..20), and its URL-content reader will send requests to POST https://api.querit.ai/v1/contents; both use Bearer authentication. Querit-specific language, site/domain, and date options remain unset so the service uses its defaults.

pi-querit — Pi

A Pi extension that registers web_search and fetch_content as first-class tools. Your agent calls them automatically whenever an answer needs the live web.

Install

pi install npm:pi-querit

API key

Run the interactive setup wizard inside Pi once:

/querit-setup

The wizard validates the key, then lets you configure persistent search defaults (result count, time range, countries, languages, domain whitelist/blacklist) and an optional fixed-model auto-summary workflow. Everything except the API key can be skipped.

• Where the key lives: ~/.pi/agent/querit-search.json (respects PI_CODING_AGENT_DIR), written with mode 0600 on POSIX.
• CI / ephemeral alternative: set the QUERIT_API_KEY environment variable. The environment variable takes precedence when both are present.
• Never put the key in chat or logs: the extension masks key input and redacts the key from every error surface.

See the pi-querit README for the full tool reference.

dsh-querit — DeepSeek Harness

A provider package for the DeepSeek Harness ctx.web capability seam. It does not register the model-facing web_search tool; the agent preset does. By default, it reuses the official applyWebFetchTool helper to register web_fetch, and routes both tools through Querit-backed providers.

Install

dsh plugin --profile web add dsh-querit

Then wire it in the profile's cordis.patch.yml:

- insert:
    - id: web-search-querit
      name: 'dsh-querit'
      config:
        apiKeyEnv: QUERIT_API_KEY
- id: web
  config:
    searchProvider: querit
    fetchProvider: querit

API key — resolved per operation in priority order:

1. QUERIT_API_KEY exported in the launching environment, or
2. the credentials store $DSH_HOME/.credentials.yaml (QUERIT_API_KEY: <key>, hot-reloaded), or
3. a literal apiKey on the web-search-querit row (least preferred — secrets should not live in composition files).

Search defaults (count, timeRange, countries, languages, includeDomains, excludeDomains, includeContent, chunksPerDoc, fetch format/timeouts) are configured on the plugin row or in the hot-reloaded $DSH_HOME/settings.yaml web-search-querit: section.

See the dsh-querit README for the full config table.

opencode-querit — OpenCode

An OpenCode plugin that registers web_search and web_fetch as custom tools next to the built-ins. Additive: OpenCode's own websearch/webfetch stay available.

Install

Add the plugin to opencode.json:

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": ["opencode-querit"]
}

Then restart OpenCode.

API key — resolved per tool call in priority order:

1. QUERIT_API_KEY environment variable (default; rename via apiKeyEnv), or
2. apiKey in the plugin options tuple (least preferred — secrets should not live in config files):

{
  "$schema": "https://opencode.ai/config.json",
  "plugin": [
    ["opencode-querit", { "count": 8, "timeRange": "m3", "languages": ["english"] }]
  ]
}

Search defaults and fetch behavior are configured the same way (count, timeRange, countries, languages, includeDomains, excludeDomains, includeContent, chunksPerDoc, fetchFormat, fetchCrawlTimeout, fetchMaxChars, maxOutputChars).

See the opencode-querit README for the full config table and local-testing instructions.

claude-code-querit — Claude Code

A Claude Code plugin that bundles a stdio MCP server exposing web_search and fetch_content, plus a /querit-ai:research skill for source-grounded answers with citations.

Install

/plugin marketplace add querit-ai/querit-plugins
/plugin install querit-ai@querit

API key — the plugin reads only the QUERIT_API_KEY environment variable, which the MCP server process inherits from the environment that launches Claude Code. There is deliberately no in-product key option: one variable covers local development, CI, and UI installs.

• Never put the key in .mcp.json, source files, shell history, chat, or logs. Tool errors redact the active key before Claude sees them.

Claude Code does not start a plugin's MCP server while a required option is unset, so configure api_key before expecting the Querit tools to appear in /mcp.

See the claude-code-querit README for the full tool reference and the safety limits.

n8n-nodes-querit — n8n

An n8n community node with Search Web and Fetch Content operations, native paired-item and Continue On Fail handling, and AI-tool support.

Install n8n-nodes-querit through n8n's community-node interface, then create a Querit API credential and paste in the API key. n8n stores it as an encrypted credential; the node never writes it into workflow JSON or execution data. See the n8n-nodes-querit README for operation details and development instructions.

zapier-querit — Zapier

A Zapier Platform CLI integration with one Search action, Find Web Search Results. Authentication is a masked custom API-key field, tested with a fixed one-result POST /v1/search.

The integration is not published to Zapier's app directory yet. Registration, the private test push, and public review all require the company-owned Zapier developer account; the zapier-querit README carries the full handoff checklist.

browserbase-querit-demo — Browserbase

A reference demo, not an installable package: it searches with Querit, then opens the top result in a Browserbase cloud browser through Playwright connectOverCDP and saves a screenshot as evidence. It needs both QUERIT_API_KEY and BROWSERBASE_API_KEY in the environment and deliberately does not read a .env file. See the browserbase-querit-demo README.

Repository layout

Each directory is an independent npm package with its own version, CI, and release cycle. There is no root workspace: the integrations have independent dependency trees, so each package keeps its own package.json, lockfile, and node_modules.

querit-plugins/
├── .claude-plugin/            # Claude Code marketplace catalog
├── pi-querit/                 # Pi extension (TypeScript, no build step)
├── dsh-querit/                # DeepSeek Harness provider package (compiled lib/ committed)
├── opencode-querit/           # OpenCode plugin (compiled lib/ committed)
├── claude-code-querit/        # Claude Code plugin (installable payload in plugin/)
├── n8n-nodes-querit/          # n8n community node (compiled for publishing)
├── zapier-querit/             # Zapier CLI integration (not published)
└── browserbase-querit-demo/   # Browserbase reference demo (not published)

Development

Work inside a package directory; the root has no scripts:

cd pi-querit && npm ci && npm run check && npm test
cd dsh-querit && npm ci && npm run check && npm run build && npm test
cd opencode-querit && npm ci && npm run check && npm run build && npm test
cd claude-code-querit && npm ci && npm run verify
cd n8n-nodes-querit && npm ci --ignore-scripts && npm run check && npm run lint && npm test && npm run build
cd zapier-querit && npm ci && npm run check && npm run build
cd browserbase-querit-demo && npm ci && npm run check && npm test && npm run build && npm run pack

The Claude Code marketplace catalog is validated separately from the repository root:

claude plugin validate . --strict
claude plugin validate ./claude-code-querit/plugin --strict

Publishing is per package. From that package's directory, run npm version <version> --no-git-tag-version so package.json and package-lock.json stay in sync, then verify and run npm publish. Releases are tagged on GitHub with the package name prefix, e.g. pi-querit@<version>.

License

MIT — see each package's LICENSE file.