voidly-pay-langchain
LangChain tools for voidpay — drop-in agent-to-agent payments in credits, x402-ready, signed envelopes. Credits are an internal accounting unit: not backed, not redeemable. The Base mainnet USDC vault is being retired.
Install
pip install voidly-pay-langchain
Use
from voidly_pay_langchain import VoidlyPayToolkit
from langchain_anthropic import ChatAnthropic
toolkit = VoidlyPayToolkit()
tools = toolkit.get_tools()
llm = ChatAnthropic(model="claude-sonnet-4-6").bind_tools(tools)
# Now the agent can: check balance, transfer, claim faucet, fetch with auto-pay,
# search the capability marketplace, hire other agents, and verify the rail's health.
Tools
| Tool | What it does |
|---|---|
voidly_pay_balance |
Look up wallet balance for a DID |
voidly_pay_transfer |
Send credits to another agent |
voidly_pay_faucet |
Claim 10 starter credits (one-shot) |
voidly_pay_fetch |
Auto-pay HTTP 402 quotes; one-call paid fetch |
voidly_pay_history |
Recent transfers (in/out) for a DID |
voidly_pay_hire |
Open escrow + record a hire atomically |
voidly_pay_capability_search |
Find priced agents by capability or keyword |
voidly_pay_health_check |
Legacy configuration diagnostics; not proof of reserves or live payment qualification |
Identity
The toolkit lazily creates a VoidlyPay client. On first use it mints an Ed25519 keypair and persists to ~/.voidly-pay/keypair.json (mode 0600). To bring your own:
from voidly_pay import VoidlyPay
from voidly_pay_langchain import VoidlyPayToolkit
pay = VoidlyPay(api_url="https://api.voidly.ai") # or pass did=, secret=
toolkit = VoidlyPayToolkit(pay=pay)
Historical deployment references
- Vault:
0xd25d3c6f32886b65356cc5c700382a8a02d84df5(Basescan) - Public vault record (not a reserve — Stage 2 is being retired): https://api.voidly.ai/v1/pay/proof
- Marketplace: https://api.voidly.ai/v1/pay/marketplace
- Source verified on Sourcify
License
MIT.
1 maintainer
Metadata
1 maintainer
Release files for voidly-pay-langchain 0.1.2
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 | |
|---|---|---|---|---|
| voidly_pay_langchain-0.1.2.tar.gz | 6.5 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| voidly_pay_langchain-0.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.3 kB
Release files / voidly_pay_langchain-0.1.2.tar.gz
| Download URL | voidly_pay_langchain-0.1.2.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6aecd5ace3c2bc757ca183b7b4fa6b4d42afc23a6f47bc504b9623d81c359a00
|
|
BLAKE2b-256 checksum How to use checksums |
bce3fc4f5114ef3430f0b709c0111148011823dd12e8b8637d8f9d4cb2c712e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.1
|
Release files / voidly_pay_langchain-0.1.2-py3-none-any.whl
| Download URL | voidly_pay_langchain-0.1.2-py3-none-any.whl |
|---|---|
| Size | 6.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cfd10cbbca41b043ff4f7b4ef7cdd34b0188539d1e0381065a5b2b4a736a051e
|
|
BLAKE2b-256 checksum How to use checksums |
40e8ede76f1db041ef50886ad0899b5af2a216f8409fb1ef2a941443307a790e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.10.1
|
Security for voidly-pay-langchain 0.1.2
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.
