Skip to main content

deepsieve-cli

Run cited deep research from your terminal.

uv tool install deepsieve-cli   # or: pipx install deepsieve-cli
deepsieve login

login opens your browser, you approve a short code, and the CLI stores a scoped API key. Nothing to copy, nothing pasted into your shell history. The credential appears in Settings → API keys on your deployment and can be revoked there at any time.

Commands

deepsieve whoami                              # identity, workspace, scopes
deepsieve runs create --query "..." --dry-run # free simulated run (~15s)
deepsieve runs create --query "..." --wait    # real run: spends credits
deepsieve runs list
deepsieve runs get <id>                       # exit 4 while still running
deepsieve runs cancel <id>
deepsieve members list                        # who is in the workspace + seat usage
deepsieve data catalog                        # entities + columns (never guess)
deepsieve data get companies --receipts       # rows with per-cell citations
deepsieve setup mcp                           # MCP registration for this origin

Add --json to anything for machine-readable output.

Profiles: several deployments side by side

deepsieve login --profile staging --origin https://staging.deepsieve.ai
deepsieve --profile staging runs list

Each profile is its own (origin, credential) pair, so staging and production never overwrite one another. DEEPSIEVE_PROFILE sets the default.

CI and containers

Skip login entirely — set DEEPSIEVE_API_KEY (and DEEPSIEVE_BASE_URL if not production). Environment variables take precedence over any stored profile.

DEEPSIEVE_API_KEY=ds_live_... deepsieve --json data get companies

What it deliberately cannot do

No billing, no organization or member management, no API-key management, and it cannot edit an active Blueprint. Those are decisions for a human in the app — and the restriction is enforced server-side by the credential's scopes, not just by the absence of a subcommand.

Starting a real (billable) run asks for confirmation, and refuses outright in a non-interactive shell unless you pass --yes.

Exit codes

Code Meaning
0 success
1 failure
2 usage error
3 not authenticated
4 run still in progress

Full docs: https://deepsieve.ai/developers/cli

Release files for deepsieve-cli 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for deepsieve-cli 0.1.1
File Size Uploaded
deepsieve_cli-0.1.1.tar.gz 16.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for deepsieve-cli 0.1.1
File Interpreter ABI Platform
deepsieve_cli-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size:29.9 kB

Release files / deepsieve_cli-0.1.1.tar.gz

Download URL deepsieve_cli-0.1.1.tar.gz
Size 16.7 kB
Tags Source
SHA-256 checksum
How to use checksums
98a9b259c1a538b27b60a6219e2e426367f8f16f862041743b97de0d35b323d2
BLAKE2b-256 checksum
How to use checksums
6b79587671005e2017e8fdaffa1cd0ef0618ce0b0680a6442195d6a3846bc180
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.

Transparency log

Release files / deepsieve_cli-0.1.1-py3-none-any.whl

Download URL deepsieve_cli-0.1.1-py3-none-any.whl
Size 13.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b7a68e986c5e3efc97f6744e38537aba7a7ad0ff2f1a5c36d2118701af17aff7
BLAKE2b-256 checksum
How to use checksums
d939c93fa43e4f0182a8d867ee107c2a98121633ff6de70ea1af646fe9ece4aa
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 4, 2026.

Transparency log

Release history Release notifications | RSS feed

0.2.0

2 release files

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page