hlido-trust
Vet AI agents before you delegate to them. hlido-trust lets your agent
call Hlido — independent, evidence-backed trust scores for
AI agents — as a trust step inside its own loop. Drop-in tools for
CrewAI and LangChain, plus a framework-agnostic client with zero
runtime dependencies (standard-library urllib only).
Hlido is independent (we don't take money to rank anyone), evidence-backed (every score links to verifiable proof), longitudinal (re-tested over time), and machine-readable. That's exactly the material an agent should check before trusting another agent or tool.
Install
pip install hlido-trust # core, zero deps
pip install "hlido-trust[crewai]" # + CrewAI tools
pip install "hlido-trust[langchain]" # + LangChain tools
pip install "hlido-trust[nemo]" # + NVIDIA NeMo Agent Toolkit plugin
Most users should just install the umbrella package —
pip install hlido(plushlido[crewai|langchain|nemo]) — one name for the whole Hlido Python surface.hlido-trustis the underlying core that the umbrella depends on.
NVIDIA NeMo Agent Toolkit
pip install "hlido[nemo]" registers the hlido function group via the
nat.plugins entry point. In a workflow config:
function_groups:
hlido:
_type: hlido # exposes hlido__trust_check, hlido__find_trusted,
# hlido__verify_claim, hlido__get_scorecard
No API key — Hlido's trust surface is public.
30-second use — a plain guard clause (no framework)
from hlido_trust import HlidoClient
hlido = HlidoClient()
if not hlido.trust_gate("aider", min_score=70):
raise RuntimeError("Aider failed the Hlido trust gate — not delegating.")
trust_gate fails closed: an agent with no Hlido review, or one carrying a
red flag, returns False.
CrewAI
from crewai import Agent
from hlido_trust.crewai_tool import hlido_crewai_tools
router = Agent(
role="Delegation Router",
goal="Only delegate to agents that pass an independent Hlido trust check.",
tools=hlido_crewai_tools(), # Hlido Trust Check + Hlido Recommend
)
LangChain
from hlido_trust.langchain_tool import hlido_langchain_tools
tools = hlido_langchain_tools() # hlido_trust_check + hlido_recommend
llm_with_tools = llm.bind_tools(tools)
See examples/ for full "vet before you delegate" agents.
API
| Call | What it does | Endpoint |
|---|---|---|
HlidoClient().recommend(need, k=1) |
Hlido-vetted agents for a free-text need, ranked | POST /v1/recommend |
HlidoClient().trust_check(slug) |
Full trust verdict for one agent (score, tier, red flags, evidence) | scorecard JSON |
HlidoClient().trust_gate(slug, min_score=70) |
Boolean go/no-go (fails closed) | scorecard JSON |
recommend returns the single top match on the free tier. Set
HLIDO_API_KEY (a hlk_live_* key from https://hlido.eu/api/) to unlock
k > 1.
HlidoClient(api_key="hlk_live_...") # or export HLIDO_API_KEY
TrustVerdict fields
slug, name, score, tier (VITAL ≥90 / STEADY ≥70 / FADING ≥40 /
FLATLINE), confidence, best_for, not_recommended_for, what_it_fails_at,
red_flags, evidence_url, stale, found. Helpers: .recommended(min_score)
and .summary().
Why
One agent that checks trust before delegating beats a thousand passive listings. Embedding Hlido as a callable step is how independent agent reviews actually get used — by humans and by agents.
License
MIT · Hlido hello@hlido.eu · https://hlido.eu
Metadata
Release files for hlido-trust 0.2.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 |
|---|---|---|---|---|
| hlido_trust-0.2.0.tar.gz | 16.5 kB | Without provenance | Details for hlido_trust-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| hlido_trust-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for hlido_trust-0.2.0-py3-none-any.whl |
Total release size: 32.2 kB
Release files / hlido_trust-0.2.0.tar.gz
| Download URL | hlido_trust-0.2.0.tar.gz |
|---|---|
| Size | 16.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8a7a85b8668cef904fcba1b20dee03a5ab9b2ceea89f5f042c0191e51bd6944a
|
|
BLAKE2b-256 checksum How to use checksums |
3cce61003ad2b148ae03b7d55b8be5996b66f9c41cd59de45d3f10a1beb182a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / hlido_trust-0.2.0-py3-none-any.whl
| Download URL | hlido_trust-0.2.0-py3-none-any.whl |
|---|---|
| Size | 15.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fe7bfafae52f245523d0f8ef6b4e9bae05593b9dfc51008988b1f008b6846770
|
|
BLAKE2b-256 checksum How to use checksums |
d13075050065ea6a998059360b4e824a96ce913a9b017e892413083681469cdc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for hlido-trust 0.2.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.