Ir al contenido

Web Search

Esta página aún no está disponible en tu idioma.

Askimo includes built-in web search tools so AI can look up current information and read live web pages when your question needs up-to-date context.


When web search is enabled, Askimo can use two built-in tools during a chat:

  • searchWeb: Finds relevant links for your query
  • readWebPage: Opens a selected URL and extracts readable content

This is useful for recent news, current prices, product comparisons, and any topic that changes over time.


  1. Open Settings from the sidebar.
  2. Select Web Search.
  3. Turn on the Enabled switch.
  4. Pick your preferred backend.
  5. Configure API key or endpoint if required.
  6. Click Test to verify the setup.

Askimo supports multiple backends:

Backend API Key Needed Notes
DuckDuckGo No Zero-config option, good default for quick setup
Brave Search Yes Requires a Brave Search API key
Tavily Yes Requires a Tavily API key
SearxNG No (usually) Use your own SearxNG instance endpoint
  • Brave Search: Add your API key in Settings → Web Search
  • Tavily: Add your API key in Settings → Web Search
  • SearxNG: Enter your instance endpoint (for example, https://your-searxng.example/search)

  1. Open or create a chat session.
  2. Open the Tools picker in the chat composer.
  3. Enable the built-in Web Search tools for that conversation.
  4. Ask your question normally, for example:
    • “Find the latest Kotlin 2.x release notes and summarize the breaking changes.”
    • “Compare current pricing for Gemini and Claude Sonnet.”
  5. Ask follow-up questions to refine or verify sources.
Web Search tools selection panel in Askimo chat

For best results, ask the AI to include links and cite sources in its response.


  • Confirm Web Search is enabled in settings.
  • Re-check API key (Brave/Tavily) for typos or expired credentials.
  • For SearxNG, verify the endpoint is reachable from your machine.
  • If you use a proxy, ensure Askimo proxy settings are correct.
  • Use a more specific query.
  • Switch to another backend and test again.
  • Ask the AI to run web search with narrower keywords and a smaller scope.