Skip to main content

regent-receipt-verify

Verify a Regent Control receipt or allow token without Regent: only the token and a JWKS you saved while the issuer was reachable. Nothing calls the network. One dependency (cryptography) for RS256.

pip install regent-receipt-verify
curl -s https://control-api.regentprotocol.org/v1/control/.well-known/jwks.json > jwks-2026-09.json   # save it now, keep it with the receipts
regent-verify @receipt.txt --jwks jwks-2026-09.json --request request.json --mandate mandate-v2-reveal.json --policy policy-v3-reveal.json --counterparty-jwks get4agent-jwks.json
from regent_receipt_verify import verify
res = verify(token, jwks, request={"tool": "stripe", "action": "charge.create", "resource": None, "args": {...}},
             mandate_reveal=reveal_from_owner, policy_reveal=policy_reveal_from_org)
res.valid, res.kind, res.claims, res.args_hash_match, res.mandate_match, res.policy_match

What it proves:

check meaning
signature (RS256, kid from the JWKS) Regent's issuer signed exactly these claims
kind receipt / allow / budget a receipt (typ receipt+jwt, aud regent-receipt) can never pass as an access token
expired receipts carry a 10-year evidence period; an allow token lives about a minute, so for evidence its expiry is a note, not a failure
args_hash_match the token authorised this exact request (tool, action, resource, args) and nothing else
mandate_match the owner's revealed mandate version (snapshot + salt, terms-v2) opens the receipt's mandate_hash
policy_match the organisation's revealed policy version (text + profile + salt, policy-v1) opens policy_hash; starter-pack decisions need only the public text
confirmation_match the settlement confirmation the counterparty (merchant, PSP, custodian) signed over the same decision, embedded in the receipt, re-verified against the counterparty's own JWKS and compared with the receipt's figures: two signatures over the same facts, checked offline. settlement_source: agent receipts have none

Key rotation: pass --jwks several times (every JWKS you saved). Exit code 0 when the signature verifies and every supplied check matches.

Test vectors are minted by the real issuer (packages/receipt-verify-vectors), and the same file drives the Node package @regent-protocol/receipt-verify.

Metadata

Release files for regent-receipt-verify 0.2.2

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

Source distribution (sdist)

Source distribution for regent-receipt-verify 0.2.2
File Size Uploaded
regent_receipt_verify-0.2.2.tar.gz 14.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for regent-receipt-verify 0.2.2
File Interpreter ABI Platform
regent_receipt_verify-0.2.2-py3-none-any.whl Python 3 none any Details

Total release size: 28.8 kB

Release files / regent_receipt_verify-0.2.2.tar.gz

Download URL regent_receipt_verify-0.2.2.tar.gz
Size 14.4 kB
Tags Source
SHA-256 checksum
How to use checksums
fb4869482da5c5089a6ef0d8aa9ea4739479891fda6fd5f9c488c79d8edae7b3
BLAKE2b-256 checksum
How to use checksums
7fd616b0ae8c7e8ded6e9eb61620a606204a658c28c96875225eba659a0dad67
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 12, 2026.

Transparency log

Release files / regent_receipt_verify-0.2.2-py3-none-any.whl

Download URL regent_receipt_verify-0.2.2-py3-none-any.whl
Size 14.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
35364d4d4a3c52942ba0b0a3f2671ccc7e06991c824da1ee4bc63af7b1c8343e
BLAKE2b-256 checksum
How to use checksums
8e6476f4e5bede3afe20018c9ae27b0e17b6635585201f2c4aab3e5b990bd10a
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 12, 2026.

Transparency log

Release history Release notifications | RSS feed

0.6.0

2 release files

0.5.0

2 release files

0.4.0

2 release files

0.3.0

2 release files

This release

0.2.2 This release

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.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