Nodes/ComfyUI Griptape Nodes/Griptape WebSearch Driver: DuckDuckGo
ComfyUI Node

Griptape WebSearch Driver: DuckDuckGo

Web search for your agent with zero API keys — DuckDuckGo just works

By griptape-ai·Created 2 years ago·Updated about a year ago· 238
Griptape WebSearch Driver: DuckDuckGo
    • DRIVER

    The DuckDuckGo WebSearch driver is the "no sign-up required" option for giving your Griptape agent live web search. Where the Google driver demands an API key and a Programmable Search Engine ID, this one has no inputs at all - no key, no config, no billing. Wire it into the Griptape Tool: WebSearch node and your agent can suddenly look things up on the real web, free.

    This is the node to grab when you want to try agentic web search before committing to any paid API. It's also a great default for experiments and personal tools where search volume is low. The trade is reliability: DuckDuckGo's unofficial search endpoint is generous for occasional use but rate-limits aggressively if your agent starts hammering it, and there's no SLA or quota dashboard like you'd get from a paid API. For a quick "does this even work" pass, it's unbeatable - you just drop it in and run.

    How it works

    It's the smallest node in the pack. The class wraps Griptape's DuckDuckGoWebSearchDriver and its create method is essentially return DuckDuckGoWebSearchDriver() - no parameters are read, nothing is configured. The driver handles the DuckDuckGo scraping internally, and when the agent's web-search tool calls it, it returns ranked results with titles, URLs, and snippets for the agent to read.

    Because there are no parameters, the node's only real output is the driver itself: WEB_SEARCH_DRIVER, which you wire into the Griptape Tool: WebSearch tool, which in turn goes into your agent's tools list. If you're using a config node, the driver can also slot into the web-search driver slot where one exists. Everything upstream and downstream of it is the same as the Google driver - the only difference is what's between the wires.

    Inputs and outputs

    None on the input side - the info schema for this node is empty. Output is the single WEB_SEARCH_DRIVER object. That's the entire surface area, and it's the reason this node is the one you reach for when you just want search to happen.

    Install

    Same pack, same install - ComfyUI Manager (search "Griptape") or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/griptape-ai/ComfyUI-Griptape
    

    The pack pulls in griptape[all] and python-dotenv from requirements.txt. On Nvidia, watch for the torch conflict the README warns about - if ComfyUI breaks after install, reinstall torch from the cu121 index. No API keys, no settings page, nothing else to configure.

    Common gotchas

    The main thing to know is that "free" has a ceiling. DuckDuckGo's backend can throttle you mid-workflow if the agent runs a burst of searches, and there's no error dashboard to tell you why searches suddenly fail. If your agent starts returning "no results" during a long run, that's often rate-limiting, not a bug - and it's the cue to graduate to the Google driver for production work. Also remember the obvious: this gives the agent search, but the agent only searches if the WebSearch tool is actually in its tools list. The driver alone does nothing.

    CategoryGriptape/Agent Drivers/Web Search

    Inputs (0)

    No inputs

    Outputs (1)

    NameTypeDescription
    DRIVERWEB_SEARCH_DRIVER