Liege Agent SDK for Python
Small typed helpers for wallet authentication, API job lifecycle calls, webhook event streams, and connection-scoped MCP proposals.
pip install liege-agent-sdk
The SDK never receives or stores a private key. Pass a signer callback to authenticate, then use
the returned session token for API calls:
from liege_agent_sdk import LiegeClient
with LiegeClient() as liege:
session = liege.authenticate(wallet_address, wallet_signer.sign_message)
for job in liege.list_jobs():
print(job.id, job.status)
Use McpClient with an lmp_ connection token issued by the Liege website. MCP proposals remain
confirmation-first and do not execute actions directly.
For experimental x402 resources, LiegeClient.request_x402(url, signer) performs the 402 handshake.
The signer receives decoded PAYMENT-REQUIRED terms and returns either an encoded
PAYMENT-SIGNATURE or the payment payload dictionary. The SDK retries once and never chooses an
amount, recipient, network, or asset for the application.
Development
python -m pip install -e '.[test]'
python -m pytest
python -m build
1 maintainer
Metadata
1 maintainer
Release files for liege-agent-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)
| File | Size | Uploaded | |
|---|---|---|---|
| liege_agent_sdk-0.1.1.tar.gz | 6.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| liege_agent_sdk-0.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.3 kB
Release files / liege_agent_sdk-0.1.1.tar.gz
| Download URL | liege_agent_sdk-0.1.1.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec37cc2590b51ff94d72e9887ddbd50a1f6e8c29c5fc3c7537b1d5d671372879
|
|
BLAKE2b-256 checksum How to use checksums |
dfd19ec5386d6908609a904eb607d335966a52dd61395e3bbf459a262b132b98
|
| 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 1, 2026.
Transparency logRelease files / liege_agent_sdk-0.1.1-py3-none-any.whl
| Download URL | liege_agent_sdk-0.1.1-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
992873abf4f3d802e149af8d58690a2a96031fdf3d426d4bebd91c0da2ab6926
|
|
BLAKE2b-256 checksum How to use checksums |
a53d9676d5a0a6e8edb33f78d938a78125268425c6b951dcf82adad510be8e8a
|
| 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 1, 2026.
Transparency log
