ainfera-verify
Trust no one. Verify the chain yourself.
ainfera-verify is the public, offline verifier for Ainfera AuditChains. It lets anyone — regulator, auditor, partner, curious developer — fetch an Agent's AuditChain and cryptographically verify it without trusting Ainfera or holding an Ainfera account.
This is the customer trust primitive behind Ainfera's audit-grade transparency claim: chain of custody you can check yourself.
Install
pip install ainfera-verify
Or with Homebrew:
brew install ainfera/tap/verify
Usage
Verify a full AuditChain by Agent ID (fetches from the public read endpoint, then verifies offline):
ainfera-verify chain manwe
Inspect a single AuditEvent:
ainfera-verify event manwe 1245
Verify an offline Annex IV bundle export (use this for air-gapped review):
ainfera-verify bundle ./manwe-2026-05-19.zip
What it verifies
For every AuditEvent in the chain:
- Hash continuity —
previous_hashmatches the prior event'sevent_hash. - Event integrity —
event_hashis the SHA-256 ofprevious_hash || canonical_json(payload). - HMAC signature —
hmac_signaturevalidates against Ainfera's published public key. - Sigstore signature — when present, validated against the Rekor transparency log.
If any check fails, the verifier reports the exact seq where the chain breaks.
Trust model
- The CLI ships under Apache 2.0. The verification logic is auditable.
- After events are fetched, verification is fully offline — no network calls, no Ainfera dependency.
- Ainfera's HMAC public key is published at
https://ainfera.ai/.well-known/ainfera-public-key.jsonand cached locally. - For air-gapped verification, download the key once or use a bundle export (which embeds the key).
EU AI Act Annex IV
Annex IV technical documentation requires verifiable evidence of system behavior. ainfera-verify bundle produces a pass/fail with the cryptographic chain of custody — sufficient evidence for a regulator's technical reviewer.
Web version
Don't want to install anything? Drop a bundle into verify.ainfera.ai. All verification runs in your browser.
License
Apache 2.0. See LICENSE.
Release files for ainfera-verify 0.1.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 | |
|---|---|---|---|
| ainfera_verify-0.1.0.tar.gz | 20.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ainfera_verify-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 36.2 kB
Release files / ainfera_verify-0.1.0.tar.gz
| Download URL | ainfera_verify-0.1.0.tar.gz |
|---|---|
| Size | 20.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e2efc24acafae7241ffc3d648186de367a0f363f6e8df3b1ae30e2a5c9f28d43
|
|
BLAKE2b-256 checksum How to use checksums |
44f8ae2eeeaa0b23dbc513c9753c51ed5c429b789c4994c3f5fd4ec09f68b53f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 14, 2026.
Transparency logRelease files / ainfera_verify-0.1.0-py3-none-any.whl
| Download URL | ainfera_verify-0.1.0-py3-none-any.whl |
|---|---|
| Size | 15.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
774a2223b5f27e7286c7e266db705b0710c5c0b14ec1db1f642ae048fe9e0d7e
|
|
BLAKE2b-256 checksum How to use checksums |
421ee1d9d3af57846a73272590bb724b61736a2c24598f397879a9ac002a28c9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 14, 2026.
Transparency log