zanii-underwrite
Insurance evidence for AI agents: build and verify the signed formats of Zanii Underwrite in Python. Pure functions, no I/O, no network. Alpha (0.x): formats may change between minor versions.
pip install zanii-underwrite
from zanii_underwrite import Refusal, verify_pack
try:
verdict = verify_pack({"pack": pack, "documents": documents, "receipt": receipt, "decisions": decisions,
"pq": pq, "purpose": purpose, "recipient": recipient, "at": at,
"trusted_signers": trusted, "seen_nonces": [], "require_pq": False})
except Refusal as r:
print("refused:", r) # the first failing rule id
What it covers:
- Risk: exposure records, loss runs, completeness proofs, insurability and readiness packs, monitoring events, renewal diff, framework crosswalk, AI-use statement, pool and portfolio views.
- Response: case logs, incident exports, playbook reports, timelines, claim packs.
- A
zanii-uw-pyCLI with the same contract as the TypeScriptzanii-uw.
Every format is canonical JSON (RFC 8785), integers only, and unknown values are None with a
reason. The TypeScript library @zanii/underwrite on npm gives the same bytes for the same input.
Zanii never insures, quotes, places or advises on cover; a licensed partner carries every regulated step. The framework crosswalk is an evidence map awaiting a compliance reviewer, not a certification. Seeds and keys named TEST ONLY are published on purpose for test vectors; a production verifier must never trust them.
License: Apache-2.0. Contact: info@zanii.agency.
Metadata
Release files for zanii-underwrite 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 | Provenance | Actions |
|---|---|---|---|---|
| zanii_underwrite-0.2.0.tar.gz | 233.3 kB | Without provenance | Details for zanii_underwrite-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| zanii_underwrite-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for zanii_underwrite-0.2.0-py3-none-any.whl |
Total release size: 496.6 kB
Release files / zanii_underwrite-0.2.0.tar.gz
| Download URL | zanii_underwrite-0.2.0.tar.gz |
|---|---|
| Size | 233.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ead5a675e37d02e5b99bbaeef609b342bd6486835743392d607d641afc1ee5f
|
|
BLAKE2b-256 checksum How to use checksums |
7c3a2c3cd91e65c806b5df1e5a7d40f6440755f2083f3d098edad2a0d548dff0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / zanii_underwrite-0.2.0-py3-none-any.whl
| Download URL | zanii_underwrite-0.2.0-py3-none-any.whl |
|---|---|
| Size | 263.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d900b8362131e7440f6c2d213d23d79c02f6550e5cda0f49fc9b4d4552d24eb7
|
|
BLAKE2b-256 checksum How to use checksums |
1bb6b170330829012c74c5132bc1c5a14a464b4177570087be9e92e56f447358
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.12.5 {"installer":{"name":"uv","version":"0.12.5","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for zanii-underwrite 0.2.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.
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.