Codestin Search App

Use the context-dev CLI to retrieve company data, scrape websites, and run other API operations from your terminal.

The CLI is generated from the API contract. Command names and flags can change between releases as that contract evolves. Use --help from your installed version as the source of truth.

Install

Release binary
Go

Download the archive or package for your operating system and architecture from the latest GitHub release.Extract context-dev, move it to a directory on your PATH, then verify it:

context-dev --version

Pin a release and verify any published checksums in CI instead of downloading latest on every run.

With Go 1.22 or newer:

go install github.com/context-dot-dev/context-dev-cli/cmd/context-dev@latest
context-dev --version

Go installs the binary under $(go env GOPATH)/bin. Add that directory to PATH if the command is not found. Replace @latest with a release tag for reproducible environments.

Set your API key

Create an account at context.dev/signup, copy a key from the dashboard, and expose it to the current shell:

export CONTEXT_DEV_API_KEY="ctxt_secret_..."

Use a secret manager in CI. Avoid the global --api-key flag for normal use because command-line arguments can appear in shell history and process listings.

Make your first request

The Brand command uses the same discriminator as POST /brand/retrieve:

context-dev brand retrieve \
  --type by_domain \
  --domain stripe.com \
  --transform 'brand.title'

The command prints the returned company name. Remove --transform to inspect the full response. Do not use older dedicated commands such as retrieve-by-name or identify-from-transaction. The current CLI uses one brand retrieve command with the appropriate --type and matching identifier flag.

# Company name
context-dev brand retrieve \
  --type by_name \
  --name "Stripe"

# Transaction descriptor
context-dev brand retrieve \
  --type by_transaction \
  --transaction-info "SQ *CORNER CAFE" \
  --country-gl us \
  --high-confidence-only

Find a command

context-dev --help
context-dev web --help
context-dev web web-scrape-md --help
context-dev brand retrieve --help

The top-level resources currently include parse, web, ai, brand, industry, utility, monitors, batch, people, and news. Common operations:

# Scrape one page to Markdown.
context-dev web web-scrape-md \
  --url https://example.com \
  --use-main-content-only

# Crawl a bounded part of a site.
context-dev web web-crawl-md \
  --url https://docs.example.com/product/ \
  --max-pages 50 \
  --max-depth 3 \
  --url-regex '^https://docs\.example\.com/product/'

# Extract a rendered design system.
context-dev web extract-styleguide \
  --domain example.com \
  --color-scheme light

# Classify a domain with NAICS.
context-dev industry retrieve-naics \
  --input example.com

# Queue a subscriber prefetch. This is not a completion signal.
context-dev utility prefetch \
  --type brand \
  --identifier.domain example.com

The examples above were checked against the generated CLI source on September 4, 2026. Run the relevant --help command when using a different release.

Control output

Use machine-readable output for scripts and transformations to keep large responses out of an agent’s context window:

# Stable JSON for a pipeline.
context-dev web web-scrape-md \
  --url https://example.com \
  --format json > page.json

# Select one field with GJSON syntax.
context-dev brand retrieve \
  --type by_domain \
  --domain stripe.com \
  --transform 'brand.colors'

Available formats and transformation behavior belong to the installed CLI version. Check context-dev --help before relying on one in automation.

Use with an agent

Add a short instruction to your repository’s agent file:

AGENTS.md

## Context.dev

The `context-dev` CLI is installed. Read `CONTEXT_DEV_API_KEY` from the
environment and never print it. Run `context-dev <resource> <command> --help`
before using an unfamiliar command. Bound crawls and batch jobs, use JSON output
for automation, and review state-changing monitor commands before running them.

Keep approval prompts enabled for commands that create, update, run, or delete monitors and batches. Do not let untrusted website content choose shell arguments.

Troubleshoot

Symptom	Check
`command not found`	Confirm the extracted binary or Go bin directory is on `PATH`.
Unknown command	Compare with `context-dev --help`; the example may target another release.
Missing required flag	Run help for that exact resource and command.
`401`	Confirm the key exists in the CLI process environment.
Unexpected JSON	Record `context-dev --version` and compare the corresponding API contract.

Next steps

Agent quickstart

Scope an integration task and verify the code your agent writes.

Connect MCP

Connect your agent to the hosted Context.dev tools.

CLI source and releases

Inspect the CLI source or download a release.

Get started

Web data

Brand data

Automation

Production

Install the CLI

Install

Set your API key

Make your first request

Find a command

Control output

Use with an agent

Troubleshoot

Next steps

Agent quickstart

Connect MCP

CLI source and releases

​Install

​Set your API key

​Make your first request

​Find a command

​Control output

​Use with an agent

​Troubleshoot

​Next steps

Agent quickstart

Connect MCP

CLI source and releases

Install

Set your API key

Make your first request

Find a command

Control output

Use with an agent

Troubleshoot

Next steps