Skip to main content

SPR SDK for Python

SPR, the Sealed Payment Record, in Python: seal your AI agents' payments on your own machine with your company's own key, and check any SPR record or package without Luca. Apache-2.0. Needs cryptography.

from spr import SprBook

book = SprBook(dir="books", agent_id="agt_research", entity="Example Co")

# Before paying: declare, and sign the nonce as the payment's nonce where the rail lets you (x402, EIP-3009).
intent = book.declare(purpose="Market data for the pricing model", max_amount_minor=20000, currency="USDC")
nonce = book.nonce_for(intent["intent_id"])
if book.check_payment(10000, "USDC", nonce=nonce)["decision"] != "approve":
    raise SystemExit("declined")

# After paying: seal it.
record = book.seal(rail="x402", source_id=tx_hash, amount_minor=10000, currency="USDC", nonce=nonce)

The folder, files and records are the same as the JavaScript SDK's, so either language opens the other's book.

The book runs on your machine and makes no call to Luca. A check against the book's own mandate.json reports authority: "self-declared", because whoever keeps the book writes it. Times need their offset; a time without one is refused. Different facts for a payment already sealed return conflict and seal nothing, unless you pass correction={"reason": ...}.

Check a package, or run the test vectors that come with the package:

python -m spr <package folder>
python -m spr --vectors

Send the book to Luca's hosted service (optional), which checks every seal, then classifies each payment and posts it to your ERP:

book.register_with_luca("acme-us", url="https://sandbox.luca.network", api_key=FINANCE_KEY)   # once, by finance
book.send_to_luca(url="https://sandbox.luca.network", api_key=LUCA_API_KEY)                    # sending it again changes nothing

url and api_key default to LUCA_URL and LUCA_API_KEY. Only the package's files are sent, never the private key.

Tests: python -m unittest discover -s tests, from this folder.

Metadata

Release files for spr-sdk 0.1.1

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

Source distribution (sdist)

Source distribution for spr-sdk 0.1.1
File Size Uploaded Provenance Actions
spr_sdk-0.1.1.tar.gz 29.0 kB With provenance Details for spr_sdk-0.1.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for spr-sdk 0.1.1
File Interpreter ABI Platform Actions
spr_sdk-0.1.1-py3-none-any.whl Python 3 none any Details for spr_sdk-0.1.1-py3-none-any.whl

Total release size: 56.4 kB

Release files / spr_sdk-0.1.1.tar.gz

Download URL spr_sdk-0.1.1.tar.gz
Size 29.0 kB
Tags Source
SHA-256 checksum
How to use checksums
afbb11c5b664758487df9e4aa83410ff41eae16b45f67d707ed6312dbcd84902
BLAKE2b-256 checksum
How to use checksums
b2d133a475ec60d29e8afd7160268c82d7d03bce19569f4be203422490676c1a
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 28, 2026.

Transparency log

Release files / spr_sdk-0.1.1-py3-none-any.whl

Download URL spr_sdk-0.1.1-py3-none-any.whl
Size 27.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
58d9bdf2d1724a856153d97c76e4ac3e0382949bfa3160cdd16537943d43b1fc
BLAKE2b-256 checksum
How to use checksums
756de4b28d991c8baa9999976b1587ed8118a39bfde109b0bae9af46ae6473e6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

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 28, 2026.

Transparency log

Security for spr-sdk 0.1.1

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for spr_sdk-0.1.1.tar.gz

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 28, 2026.

Transparency log

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.

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