Web Search
Steinkauz supports web search as a Native Tool inside chat. When the tool is enabled and at least one Tool backend is eligible for the current chat provider, the model can search the web and use the results in its reply.
Tool backends
Workspace admins configure an ordered list of search backends under Settings → Native Tools. The first backend that is allowed for the turn is used (no automatic retry on another backend if a call fails).
| Backend | Who can use it | Environment class | Billing |
|---|---|---|---|
| Gateway — Perplexity / Exa / Parallel (each is its own list entry) | Gateway plans on public Steinkauz, when the chat model uses the Steinkauz Gateway provider | Inherited from the Steinkauz Gateway provider (typically E1) | Charged to the subscription Gateway budget. Search fees are included in the chat step’s total cost, with an inference vs web-search breakdown in Usage, Generation details, and Tool activity. |
| SearXNG (one entry per configured instance) | All plans; usable on BYOK and private / on-prem when the instance’s Environment class is high enough for the chat provider | Inherited from that SearXNG provider connection | You run or mount the instance; Steinkauz only audits invocations (no Steinkauz search fee) |
Example: order Gateway Perplexity first, then a private SearXNG. Gateway chat uses Perplexity when eligible; a BYOK chat on a higher Environment class can still use SearXNG without switching the whole workspace off Gateway search.
Gateway backends require both a Gateway plan and a Gateway chat model. SearXNG is added as an Inference Provider (integration “SearXNG”), with base URL, optional API key, and an environment class (E-class) for routing and Tool-backend eligibility.
How it works
- You ask a question in chat. If the model needs up-to-date information, it can call the web search tool.
- Results are returned to the model; you see sources in the tool card when available.
- If no backend is eligible (for example only Gateway search is configured but the chat model is BYOK, or Environment class rules out every backend), Web Search stays in the Tools popover but is disabled with an explanation — Steinkauz does not fall back to a Steinkauz-paid Gateway search path.
- The Tools popover can show which backends are eligible under the current chat provider; members do not override the admin order.
Approval
SearXNG can require approval before running (shown in chat when the model invokes the tool). Gateway search backends run as part of the Gateway request and cannot wait for that approval step. If the tool is set to require approval, Gateway backends are marked unsupported in settings and skipped for eligibility; a later SearXNG backend in the list may still run.
Configure approval behavior under Settings → Native Tools. See Tool policies.
Privacy and providers
Search queries leave Steinkauz toward the chosen backend. Usage and routing follow your plan and Data handling. Backend Environment class and provider environment / data routing still apply. See also Usage, costs, and activity details.