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.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| deepsieve_cli-0.2.0.tar.gz | 18.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deepsieve_cli-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size:31.8 kB
Release files / deepsieve_cli-0.2.0.tar.gz
| Download URL | deepsieve_cli-0.2.0.tar.gz |
|---|---|
| Size | 18.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5a9df8acf8d4b3a0a0563913077c34cbdfda12ba40144d773fee976a80217ac6
|
|
BLAKE2b-256 checksum How to use checksums |
eac327be7fba3aea550236230c11631cc32cda430391432347a7b6f04837ebd1
|
| 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 9, 2026.
Transparency logRelease files / deepsieve_cli-0.2.0-py3-none-any.whl
| Download URL | deepsieve_cli-0.2.0-py3-none-any.whl |
|---|---|
| Size | 13.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4157a7807675a09829977e6962f147643d121a6816f9167d254aab2c0235d7ec
|
|
BLAKE2b-256 checksum How to use checksums |
edeb4a424c067ed4ff4ad4695b74f288c006eff2221b5ccd35b663d441be8a61
|
| 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 9, 2026.
Transparency log