langchain-clearsigned
A LangChain tool that gives any agent an adversarial verify step: Clearsigned checks one factual
claim against live web evidence and returns SUPPORTED, REFUTED or UNVERIFIABLE with a
confidence that is a measured realized rate from a published calibration curve, every source
with its stance, and an Ed25519-signed receipt this tool verifies offline against Clearsigned's
pinned published key before any of it reaches the agent.
Each call pays $0.05 USDC over x402 (Base mainnet) from a key you hold. The price never depends
on the verdict; refunds exist only for failure to deliver. UNVERIFIABLE is a real answer: the
engine abstains rather than guesses.
Install
pip install langchain-clearsigned
export CLEARSIGNED_BUYER_KEY=0x… # an EVM key holding a little USDC on Base mainnet
Use
from langchain_clearsigned import ClearsignedVerifyTool
from langgraph.prebuilt import create_react_agent
agent = create_react_agent(model, [ClearsignedVerifyTool()])
agent.invoke({"messages": [("user", "Is it true that the Eiffel Tower is in Paris? Verify first.")]})
The tool returns a JSON string:
{"verdict": "SUPPORTED", "confidence": 0.914,
"confidence_meaning": "measured realized rate under engine-pkg-groq-20260925-n204",
"evidence": [{"source": "https://en.wikipedia.org/wiki/Eiffel_Tower", "stance": "supports"}],
"receipt_id": "…", "signature_verified_offline": true}
A receipt whose signature does not verify comes back as RECEIPT_SIGNATURE_INVALID and nothing
from it is passed on. Verdicts take about 5 to 15 seconds.
Without a wallet
buy_verdict(claim, exchange=..., pinned=...) accepts an injected exchange function and pinned
key, which is how the package's own tests run: no network, no wallet, receipts signed with a
throwaway key through the production recipe.
How to check Clearsigned
- Pin the key at https://verify.clearsigned.com/pubkey (this tool does).
- Walk the public hash-chained receipt ledger at https://verify.clearsigned.com/ledger/verify.
- Live quality figures: https://clearsigned.com/quality · serving curve: https://clearsigned.com/stats.json.
Source of truth
Developed in the Clearsigned monorepo (products/langchain-clearsigned/) and mirrored to
https://github.com/diawest82/langchain-clearsigned. Changes land in the monorepo first.
Metadata
Release files for langchain-clearsigned 0.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 |
|---|---|---|---|---|
| langchain_clearsigned-0.1.0.tar.gz | 6.5 kB | Without provenance | Details for langchain_clearsigned-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| langchain_clearsigned-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for langchain_clearsigned-0.1.0-py3-none-any.whl |
Total release size: 13.1 kB
Release files / langchain_clearsigned-0.1.0.tar.gz
| Download URL | langchain_clearsigned-0.1.0.tar.gz |
|---|---|
| Size | 6.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ea1f3dabd8fbecf6a38d782f2b7d03e7a7f37d85972ca74f29d19e7dad683dbf
|
|
BLAKE2b-256 checksum How to use checksums |
62518b22263b1d6c99a2a8fe4a17846bbc8798af7cdde635840cc5cc8ed1b139
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.14
|
Release files / langchain_clearsigned-0.1.0-py3-none-any.whl
| Download URL | langchain_clearsigned-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d1170d4944361e651c588a4e01915231d915913c53a63594c152e479c8bb5358
|
|
BLAKE2b-256 checksum How to use checksums |
695149e55ecdcef62a4d84c9f870ea29809945f2688d45ac296fddcf1c4cc87e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.11.14
|
Security for langchain-clearsigned 0.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.