Vinc for Python and the terminal
Install the SDK and the vinc command together:
pip install vincs
vinc --help
vinc --version
Use the account graph from the terminal with a member key created in your Vinc
account. Set VINC_API_KEY in your environment, then run:
vinc --target account whoami
vinc --target account search --query "release checklist"
Read a node with vinc node get <id>, then send its rev as expected_rev when
editing a fragment. props_patch is JSON Merge Patch and requires that revision;
props retains its existing whole-value replacement behavior. --create-only
refuses existing identities. Documents accept --expected-content-hash from the
previous read.
vinc delete <id> --dry-run, vinc doc rm --id <id> --dry-run,
vinc edge delete --from <id> --to <id> --type <type> --dry-run, and
vinc merge nodes <keep> <drop> --dry-run return a bounded complete preview or
refuse it. Review deleted and retained content, then pass its --preview-digest
with --yes; changed affected state conflicts before mutation. The merge preview
lists unsupported edges and any relationship properties the existing merge loses.
For a write whose response might be lost, generate a fresh lowercase UUID and pass
--operation-id <uuid>. vinc operation status <uuid> reads that space's receipt.
An identical retry uses the stored result without applying again; changed arguments
conflict. accepted and unknown do not prove nonapplication. committed proves a
graph transaction; published persistence is confirmed only by
durability: published_generation in the write response. Receipts are retained
until owner purge, bounded to 5000 per owner, and contain result summaries rather
than authored text. Replayed results are historical; read the current targets.
CLI, MCP and REST never retry uncertain writes automatically.
The account CLI uses the same commands and error handling as the desktop's CLI. This Python install does not bundle the native local database, extensions or embedding model. For a self-contained local CLI, use the signed terminal download from the CLI installation guide.
from vinc import Vinc, AsyncVinc
client = Vinc() # reads VINC_API_KEY
answer = client.brief("release checklist")
Choose integrations using one package name:
pip install "vincs[langgraph]"
pip install "vincs[agent-framework]"
pip install "vincs[all]"
from vinc.integrations.langgraph import get_vinc_context
from vinc.integrations.agent_framework import VincContextProvider
These modules are built from the same source as vinc-client, vinc-langgraph
and vinc-agent-framework. Existing installations and imports keep working;
the unified package does not overwrite their files. Framework imports require
the corresponding extra. Importing the base SDK does not load a framework or
start a local database. No conversation is automatically written to Vinc.
The Python distribution version is independent of the product version reported
by vinc --version. See the SDK guide for
key types, read-only use and explicit writes.
Metadata
Release files for vincs 0.1.5
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 | |
|---|---|---|---|---|
| vincs-0.1.5.tar.gz | 1.1 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vincs-0.1.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 2.3 MB
Release files / vincs-0.1.5.tar.gz
| Download URL | vincs-0.1.5.tar.gz |
|---|---|
| Size | 1.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8b4c28e7b11d1778c40ab6c199277f2b290632bcff96119f218b7855a6f1a1a3
|
|
BLAKE2b-256 checksum How to use checksums |
fc63e10c0da2462a8c7d38726d16752fb41d04d56357772f2b320538d5c3d674
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logRelease files / vincs-0.1.5-py3-none-any.whl
| Download URL | vincs-0.1.5-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c59f284e6948aa04a5e90c1a69f84dbcff0d5a50f0b9ecba64757aa32a0556bd
|
|
BLAKE2b-256 checksum How to use checksums |
8da152a441a0bcfc26b66c2e6173bd9af1cc02cd04f3321cd0d446dc2acf6bae
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 22, 2026.
Transparency logSecurity for vincs 0.1.5
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 vincs-0.1.5.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 22, 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.