duckduckgo-cli

README

duckduckgo

DuckDuckGo instant answers CLI

duckduckgo is a single pure-Go binary. It reads public duckduckgo data over plain HTTPS, shapes it into clean records, and prints output that pipes into the rest of your tools. No API key, nothing to run alongside it.

The same package is also a resource-URI driver, so a host program like ant can address duckduckgo as duckduckgo:// URIs.

Install

go install github.com/tamnd/duckduckgo-cli/cmd/duckduckgo@latest

Or grab a prebuilt binary from the releases, or run the container image:

docker run --rm ghcr.io/tamnd/duckduckgo:latest --help

Usage

duckduckgo page <path>                      # fetch one page as a record
duckduckgo page <path> -o json              # as JSON, ready for jq
duckduckgo page <path> --template '{{.Body}}'  # just the readable body text
duckduckgo links <path>                     # the pages it links to, one per line
duckduckgo --help                           # the whole command tree

Every command shares one output contract: -o table|markdown|json|jsonl|csv|tsv|url|raw, --fields to pick columns, --template for a custom line, and -n to limit. The default adapts to where output goes (a color-aware table on a terminal, JSONL in a pipe), so the same command reads well by hand and parses cleanly downstream.

This is a fresh scaffold. It ships one example resource type, page, wired end to end. Model the real duckduckgo records in duckduckgo/ and declare their operations in duckduckgo/domain.go; each one becomes a command, an HTTP route, and an MCP tool at once.

Serve it

The same operations are available over HTTP and as an MCP tool set for agents, with no extra code:

duckduckgo serve --addr :7777    # GET /v1/page/<path>  returns NDJSON
duckduckgo mcp                   # speak MCP over stdio

Use it as a resource-URI driver

duckduckgo registers a duckduckgo domain the way a program registers a database driver with database/sql. A host enables it with one blank import:

import _ "github.com/tamnd/duckduckgo-cli/duckduckgo"

Then ant (or any program that links the package) dereferences duckduckgo:// URIs without knowing anything about duckduckgo:

ant get duckduckgo://page/<path>   # fetch the record
ant cat duckduckgo://page/<path>   # just the body text
ant ls  duckduckgo://page/<path>   # the pages it links to, each addressable
ant url duckduckgo://page/<path>   # the live https URL

Development

cmd/duckduckgo/   thin main: hands cli.NewApp to kit.Run
cli/                 assembles the kit App from the duckduckgo domain
duckduckgo/                the library: HTTP client, data models, and domain.go (the driver)
docs/                tago documentation site

make build      # ./bin/duckduckgo
make test       # go test ./...
make vet        # go vet ./...

Releasing

Push a version tag and GitHub Actions runs GoReleaser, which builds the archives, Linux packages, the multi-arch GHCR image, checksums, SBOMs, and a cosign signature:

git tag v0.1.0
git push --tags

The Homebrew and Scoop steps self-disable until their tokens exist, so the first release works with no extra secrets.

License

Apache-2.0. See LICENSE.