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. It checks each payment against the agent's declared intent: the cap, the expiry, and whether the intent was withdrawn. An optional mandate.json in the folder adds one limit across all the agent's intents; whoever keeps the folder writes it, so results report it as authority: "self-declared". Spending authority granted by someone else needs that party's own record, such as a mandate approved in Luca's hosted service.

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": ...}.

Export the book for an auditor or a counterparty (never share the folder itself, which holds the private key), and check it, or run the test vectors that come with the package:

out = book.export_package("books-export")   # out["verified"] is True: the export checked itself
python -m spr books-export --key company-public-key.pem   # every seal, file hash and intent link, and whose package it is
python -m spr --vectors           # this package against the format's test vectors

book.rotate_key(reason=...) replaces the key: the old key seals a handover to the new one in keys.jsonl, and records sealed before stay checkable. Several processes can use one book: each write takes book.lock for a moment, so nothing is lost.

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. The address must be https, and a redirect is refused; LUCA_ALLOW_INSECURE_LOCAL=1 allows plain HTTP to your own computer, for development. A book folder inside OneDrive, Dropbox, iCloud or Google Drive is refused unless you pass allow_synced_folder=True. Only the package's files are sent, never the private key. A book over one import's limits (4,000 records or 8 MB) goes in parts, each of which checks on its own.

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

Metadata

Release files for spr-sdk 0.1.5

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.5
File Size Uploaded Provenance Actions
spr_sdk-0.1.5.tar.gz 40.9 kB With provenance Details for spr_sdk-0.1.5.tar.gz

Built distribution (wheel)

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

Total release size: 78.2 kB

Release files / spr_sdk-0.1.5.tar.gz

Download URL spr_sdk-0.1.5.tar.gz
Size 40.9 kB
Tags Source
SHA-256 checksum
How to use checksums
d27dfe6f72420797768f398e5727d2b0410d22333d5b047af9b3832715b5238e
BLAKE2b-256 checksum
How to use checksums
264c5e053ad86726f8af250de4d7d18966e63939e443354a6a4f428a1825220c
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 31, 2026.

Transparency log

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

Download URL spr_sdk-0.1.5-py3-none-any.whl
Size 37.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
65e8533b6fdc809c201637a4f8d22a0a4a3d7045e05089daa20116880d13b5c0
BLAKE2b-256 checksum
How to use checksums
f5593d68000fbb491ba91c9b09b2544cdfb2c266bb36c774ec751bd97d562688
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 31, 2026.

Transparency log

Security for spr-sdk 0.1.5

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.5.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 31, 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