pulr-sdk
Official Python SDK for pulr.ai — secure file exchange for AI agents. Zero runtime dependencies; downloads are SHA-256-verified client-side.
pip install pulr-sdk # core (stdlib only)
pip install pulr-sdk[verify] # + Ed25519 receipt verification
pip install pulr-sdk[langchain] # + LangChain tools
from pulr import PulrClient, verify_receipt
pulr = PulrClient() # reads PULR_API_KEY
artifact = pulr.upload(
file_path="q3-report.pdf",
expires_in="48h",
approval=True, # link stays dormant until a human approves on the review page
provenance={"workflow": "quarterly-report", "model": "claude-fable-5"},
restrictions={"allow_countries": ["US"]},
)
print(artifact["review_url"])
# once approved — anyone with the link fetches, integrity-verified
data, sha256 = pulr.fetch_capability(artifact["download_url"])
# Ed25519-signed proof of hash + provenance + scan + approval
receipt = pulr.receipt(artifact["artifact_id"])
assert verify_receipt(receipt) # needs [verify] extra
LangChain agents:
from pulr.langchain_tool import pulr_tools
tools = pulr_tools(PulrClient()) # pulr_upload / pulr_fetch / pulr_share StructuredTools
Full API: upload, get, download, fetch_capability, share, list, revoke, receipt / verify_receipt, whoami, usage, audit, create_key, set_webhook. Get a workspace + key at pulr.ai/app.
MIT © Tal Eilon
Sealed handoff — no link at all
When the recipient has a pulr workspace, send straight to their address (pa_...):
pulr.send("pa_...", file_path="deck.pdf", message="final version")
# recipient side
offers = pulr.inbox() # sender, agent id, Ed25519 status, scan, sha256
pulr.accept(offers[0]["offer_id"]) # integrity-verified copy enters the workspace
# or: pulr.reject(offers[0]["offer_id"])
pulr.address() # your own receiving address
pulr.set_address(rotate=True) # old address dies instantly
No capability URL is ever created; both sides' receipts carry a handoff block.
Metadata
Release files for pulr-sdk 0.4.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 | Provenance | Actions |
|---|---|---|---|---|
| pulr_sdk-0.4.0.tar.gz | 5.9 kB | Without provenance | Details for pulr_sdk-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pulr_sdk-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for pulr_sdk-0.4.0-py3-none-any.whl |
Total release size: 12.8 kB
Release files / pulr_sdk-0.4.0.tar.gz
| Download URL | pulr_sdk-0.4.0.tar.gz |
|---|---|
| Size | 5.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
df755aaad02eb9582dab5b468130b83ec1e6b4ba85541cc284ce3aeedd821af1
|
|
BLAKE2b-256 checksum How to use checksums |
09f49970de633db41ede9fc8c76bfdc0fc4165161ba66afc06d2dcde726d835f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / pulr_sdk-0.4.0-py3-none-any.whl
| Download URL | pulr_sdk-0.4.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
923ecb5446015f7b632c9bc0fa6fa9f38a44606de0a2c1040fd783e78bc225eb
|
|
BLAKE2b-256 checksum How to use checksums |
d536fd40fc1a5c1e206ff44e2dce79a3a38eebba0ed77e1781429d70c6f7f708
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for pulr-sdk 0.4.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.