versyn
Cryptographic proof for AI decisions. Sign every AI decision with Ed25519, verify it offline against a pinned public key. Signing goes through the API; verification is local and free. 100% verification coverage, zero per-check cost.
pip install versyn
The problem: the "trust tax"
Most AI-monitoring tools audit decisions by sending each one to another large model to judge it. That costs money per check, so teams sample — they audit 1% and hope the other 99% was fine. Every un-audited decision is a blind spot a regulator or a lawsuit can walk into.
versyn removes that tax. Each decision is signed via the Versyn API (the event is sent to be signed). Verification, by contrast, is a signature check on your own machine — no server call, no external model, no per-check fee. You can certify 100% of decisions instead of a sample, at effectively zero marginal cost.
Verify a decision offline
from versyn import VersynClient
client = VersynClient(api_key="vk_...")
event = {
"kind": "agent.decision",
"payload": {"agent": "underwriter", "action": "decline", "reason": "DTI_too_high"},
}
cert = client.certify(event)
print(client.verify(cert, original_event=event)) # True — local, no network
verify() runs entirely on your machine. It checks that the signature is valid against the pinned public key, and that the certificate hash binds to your event. Change one field and verification refuses it.
Get a free key
import versyn
key = versyn.register("you@company.com") # 500 certifications/month, free
It survives outages
If the API is unreachable or credits run out, certify() queues the event to a durable local file (atomic writes, thread-safe) instead of losing it. On restart the client reloads the queue; flush_queue() settles it later. No silent gaps.
Verify against the published key yourself
The pinned key ships in the package and is also published at:
https://versyn.dev/.well-known/versyn-pubkey.txt
What this is — and isn't
A versyn certificate proves a specific decision was signed at a specific time and has not been altered since. It is tamper-evident, independently verifiable evidence.
It does not, by itself, prove the decision was correct or lawful, and it is not regulatory compliance certification. It is the verifiable evidence layer your governance and auditors build on top of.
License
MIT
Metadata
Release files for versyn 0.2.2
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 | Actions |
|---|---|---|---|---|
| versyn-0.2.2.tar.gz | 17.9 kB | Without provenance | Details for versyn-0.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| versyn-0.2.2-py3-none-any.whl | Python 3 | none | any | Details for versyn-0.2.2-py3-none-any.whl |
Total release size: 29.9 kB
Release files / versyn-0.2.2.tar.gz
| Download URL | versyn-0.2.2.tar.gz |
|---|---|
| Size | 17.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
84140edeacf3b1f32fba828fdbdf2f2d07828fab6cd03cdd2b5eaf72f283626e
|
|
BLAKE2b-256 checksum How to use checksums |
19e18c00d18127f5fffd66e6ccd87a362a964115a96425db11fedb6e0bce2224
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Release files / versyn-0.2.2-py3-none-any.whl
| Download URL | versyn-0.2.2-py3-none-any.whl |
|---|---|
| Size | 12.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
514222556223d573e2b043f1413e676934e07c7eced83197fed81fe1868c1794
|
|
BLAKE2b-256 checksum How to use checksums |
8e0113330de0340fcfd3e9793e9595d791664e1f03bedcce6a6a3bc66f79e5b8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.5
|
Security for versyn 0.2.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.