Agnify CLI
agnify is the command-line client for Agnify, a
video-analysis platform. Drive pipelines, upload media, run executions, manage
cameras, and query events — all from your terminal.
Install
One line (installs uv if needed, then the CLI):
curl -LsSf https://app.agnify.ai/install.sh | sh
Or, if you already have a Python toolchain:
uv tool install 'agnify[keyring]' # recommended — OS keychain for tokens
# or
pipx install 'agnify[keyring]'
# or
pip install 'agnify[keyring]'
The [keyring] extra stores your refresh token in the OS keychain (macOS
Keychain, Secret Service, Windows Credential Manager). Plain agnify also
works — it falls back to a 0600 file under ~/.config/agnify/.
Authenticate
agnify login # device-code flow in your browser
agnify whoami # confirm the active user + org
For CI / cron / integrations, skip login and set an org-scoped API key:
export AGNIFY_API_KEY=ak_… # minted in the Agnify dashboard
export AGNIFY_API_BASE=https://app.agnify.ai
Self-hosted? Point the CLI at your backend with AGNIFY_API_BASE.
Use
agnify nodes list # the pipeline node menu
agnify ingest file ./clip.mp4 --pipeline <template> --wait # upload + run + wait for results
agnify run ls # list executions
agnify events tail # stream live pipeline events
Full command reference: https://app.agnify.ai/docs/cli
To import historical footage into a camera, supply its original start time
explicitly, including Z or a UTC offset:
agnify camera stream cam-EXAMPLE --source ./footage.mp4 \
--recorded-at 2026-08-01T09:00:00Z
Each segment is timestamped at that start time plus its actual position in the video. This option requires a local video file; it does not read recording dates from video metadata. Without it, streaming uses the current wall clock.
License
Apache-2.0 © 2026 Fewbits Inc. (Agnify).
Metadata
Release files for agnify 0.15.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 | Provenance | |
|---|---|---|---|---|
| agnify-0.15.0.tar.gz | 125.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| agnify-0.15.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 199.1 kB
Release files / agnify-0.15.0.tar.gz
| Download URL | agnify-0.15.0.tar.gz |
|---|---|
| Size | 125.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3326a97ac403493312e5b0e0e53c86f40dfec62b8c7a6d1bfd517e24d80755d4
|
|
BLAKE2b-256 checksum How to use checksums |
03c937d73663c9b2842d5a56012669cb23e0ca7fc3f9647e912a71e021df9b62
|
| 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 Oct 5, 2026.
Transparency logRelease files / agnify-0.15.0-py3-none-any.whl
| Download URL | agnify-0.15.0-py3-none-any.whl |
|---|---|
| Size | 73.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
700bccc352f019f9ad8b71afb1258b4e146dee484d7d338c3627b8157c840660
|
|
BLAKE2b-256 checksum How to use checksums |
5f2f004c175b47185bc1ffa9d480ef68047d2b9d61b1a921b0c819a646c037f7
|
| 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 Oct 5, 2026.
Transparency logSecurity for agnify 0.15.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for agnify-0.15.0.tar.gz
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 Oct 5, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
