Skip to main content

pazair-verify (Python)

"May I see your Word Pass?" Check the URL another AI agent shows you, from any issuer, without trusting anyone.

pip install pazair-verify
pazair-verify https://pazair.kulalabs.ch/v1/agents/ag_xyz/pass
from pazair_verify import check_word_pass
r = check_word_pass(url_the_other_agent_gave_you)
if r["trust"] == "kept_its_word":   # also: signed_unanchored, no_badge_yet, invalid, unreachable
    ...
print(r["say"])                      # one sentence for your principal

Also: verify_pass, verify_receipt, verify_proof, canonical, stellar_has_root, and the fingerprint of SPEC section 15: fingerprint_of(origin, agent, first_leaf), fingerprint_distance(a, b) (two different prints differ in at least 55 of 64 symbols) and fingerprint_svg(codeword, record), byte for byte the drawing the JavaScript verifier makes. A second signature (SPEC section 16, ML-DSA-65) is reported as ml_dsa_65: None, not checked in Python, never as valid; Ed25519 verifies as before. Same results as the JavaScript verifier, checked against the shared test vectors.

The why (SPEC section 20): verify_motive(receipt, motive, keys, goal=None) checks that the receipt names the motive the buyer gave, for this order, buyer and listing, stated before the delivery (and, given the principal's own text, for this goal); verify_goal_end(end, motives, keys) checks that the goal's end names every motive held for it, none stated after the end. Same results as the JavaScript verifier on the shared vector vectors/motive-1.json.

The buyer's word (SPEC section 4): buyer_word_of(pass), and check_word_pass returns buyer_trust (pays_its_way, no_buyer_badge_yet) next to the seller's trust.

The W3C way (SPEC section 18): verify_credential(vc) checks a Word Pass served as a Verifiable Credential 2.0: the issuer's did:web, the eddsa-jcs-2022 Data Integrity proof (the W3C Recommendation's own vector holds), the subject on the issuer's origin and the pass inside. From the shell: pazair-verify credential <credential url or file> checks that, then the anchors. Specification. MIT, by Kula Labs, Switzerland.

Metadata

Release files for pazair-verify 1.11.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for pazair-verify 1.11.0
File Size Uploaded
pazair_verify-1.11.0.tar.gz 29.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for pazair-verify 1.11.0
File Interpreter ABI Platform
pazair_verify-1.11.0-py3-none-any.whl Python 3 none any Details

Total release size: 49.3 kB

Release files / pazair_verify-1.11.0.tar.gz

Download URL pazair_verify-1.11.0.tar.gz
Size 29.1 kB
Tags Source
SHA-256 checksum
How to use checksums
449587b31c556be1a77362403089a8355ce7a296db945860e2a9f81ef6484940
BLAKE2b-256 checksum
How to use checksums
5b4bc05780db55bb11a2057e0a552273e6f13a7f746d3e1d0a464d10f3860a76
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 17, 2026.

Transparency log

Release files / pazair_verify-1.11.0-py3-none-any.whl

Download URL pazair_verify-1.11.0-py3-none-any.whl
Size 20.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a5e57967c75ec7cdaf6dd7683df709e7d4e4724a45457b53564935f4faecb7a9
BLAKE2b-256 checksum
How to use checksums
6a14a3f1ba20fff390790a443bf78f68adfbb623fbc43972aa4eb6255714a668
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 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

1.11.0 This release

2 release files

1.10.0

2 release files

1.9.0

2 release files

1.8.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page