sardis-browser-use
Sardis payment tools for Browser Use — enable browser automation agents to make policy-controlled USDC payments with built-in spending limits and audit trails.
Install
pip install sardis-browser-use
Quick Start
Step 1: Create a Sardis wallet with a spending policy.
Step 2: Register Sardis actions on your Browser Use controller.
Step 3: Run your agent — it can now check balances, verify policies, and pay.
import asyncio, os
from browser_use import Agent, Controller
from sardis import SardisClient
from sardis_browser_use import register_sardis_actions
controller = Controller()
# Simulation mode — no API key required
client = SardisClient()
wallet = client.wallets.create(name="shopping-agent", policy="Max $100/day")
os.environ["SARDIS_WALLET_ID"] = wallet.id
register_sardis_actions(controller)
async def main():
agent = Agent(
task="Find the cheapest USB-C cable on Amazon and buy it if under $15",
controller=controller,
)
await agent.run()
asyncio.run(main())
This gives your agent three actions:
sardis_pay(amount, merchant, purpose)— execute a paymentsardis_balance(token)— check current wallet balancesardis_check_policy(amount, merchant)— verify a purchase before committing
Docs
Metadata
Release files for sardis-browser-use 1.1.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 |
|---|---|---|---|---|
| sardis_browser_use-1.1.0.tar.gz | 9.2 kB | Without provenance | Details for sardis_browser_use-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sardis_browser_use-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for sardis_browser_use-1.1.0-py3-none-any.whl |
Total release size: 15.9 kB
Release files / sardis_browser_use-1.1.0.tar.gz
| Download URL | sardis_browser_use-1.1.0.tar.gz |
|---|---|
| Size | 9.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e4eb4e63b18f6edccb2a262009678455d12f40a4db31a90ec212a23c52b6f359
|
|
BLAKE2b-256 checksum How to use checksums |
5a36d7f79d6382550e111b9e060968739cc4ad8b1149ef8ac1316e66a7dc1f24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / sardis_browser_use-1.1.0-py3-none-any.whl
| Download URL | sardis_browser_use-1.1.0-py3-none-any.whl |
|---|---|
| Size | 6.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
affcc3ed71a0cdfc091d06ca64d7244668c5a92aeac37a7b083f622d1dae7aed
|
|
BLAKE2b-256 checksum How to use checksums |
c9f3bed4f9cc138ac26254ef53f13ed11a2ba9f115966b5ab97e7b881df7d847
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.9.22 {"installer":{"name":"uv","version":"0.9.22","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for sardis-browser-use 1.1.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.