ZARQ LangChain Tool
Add crypto risk intelligence to any LangChain agent. Check if a token is safe before trading.
Quick Start (3 lines)
from zarq_langchain import ZARQRiskCheck
tools = [ZARQRiskCheck()]
agent = initialize_agent(tools, llm, agent=AgentType.OPENAI_FUNCTIONS)
Installation
pip install zarq-langchain
Dependencies: langchain-core, httpx, pydantic
Usage
As a standalone tool
from zarq_langchain import ZARQRiskCheck
tool = ZARQRiskCheck()
print(tool.run("bitcoin"))
# ZARQ Risk Check: Bitcoin (BTC)
# Verdict: WARNING
# Trust Score: 74.52/100 (Rating: A2)
# Crash Probability: 0.3177
# Distance to Default: 3.03
# ...
In a LangChain agent
from langchain_openai import ChatOpenAI
from langchain.agents import initialize_agent, AgentType
from zarq_langchain import ZARQRiskCheck
llm = ChatOpenAI(model="gpt-4")
tools = [ZARQRiskCheck()]
agent = initialize_agent(tools, llm, agent=AgentType.OPENAI_FUNCTIONS)
result = agent.run("Is it safe to buy solana right now?")
With LangGraph
from zarq_langchain import ZARQRiskCheck
from langgraph.prebuilt import create_react_agent
tools = [ZARQRiskCheck()]
agent = create_react_agent(model, tools)
Async support
result = await tool.arun("ethereum")
Custom API endpoint
# Point to a local instance or proxy
tool = ZARQRiskCheck(api_base="http://localhost:8000")
What the tool returns
The tool returns a formatted string that any LLM can reason about:
ZARQ Risk Check: Bitcoin (BTC)
Verdict: WARNING
Trust Score: 74.52/100 (Rating: A2)
Crash Probability: 0.3177
Distance to Default: 3.03
Structural Weakness: Yes
Price: $70825.0
CAUTION: Elevated risk. Proceed with reduced position size.
Verdicts:
SAFE— No structural issues detectedWARNING— Elevated risk, structural weakness presentCRITICAL— Structural collapse detected, avoid trading
API Details
- Endpoint:
GET https://zarq.ai/v1/check/{token} - Auth: None required
- Rate limit: 5,000 calls/day per IP (free forever)
- Coverage: 205 tokens
- Latency: <100ms typical
Links
- API Docs: https://zarq.ai/docs
- Full API: https://zarq.ai/v1/check/bitcoin
- Track Record: https://zarq.ai/track-record
Metadata
Release files for zarq-langchain 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 | |
|---|---|---|---|---|
| zarq_langchain-0.1.0.tar.gz | 3.8 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zarq_langchain-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 8.1 kB
Release files / zarq_langchain-0.1.0.tar.gz
| Download URL | zarq_langchain-0.1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
95c1902f4073d3540855a74b2bda8db4ae79bc91472a61233ab3156bcf315db0
|
|
BLAKE2b-256 checksum How to use checksums |
dd54f0877e76f76b38633b867b62249ec7e7261805776120de8ce12cb341f2d8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / zarq_langchain-0.1.0-py3-none-any.whl
| Download URL | zarq_langchain-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b3da93da073401b4ecac816237151bf100ccafe5c76c9c5a13727866f973d769
|
|
BLAKE2b-256 checksum How to use checksums |
ba78e39cf6eb01a5b64f7addd9884215b1b081271a8928a383332a737877aacc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for zarq-langchain 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.