docs: add Hlido to the third-party plugins acknowledgment#2095
Open
ankitkapur1992-hlido wants to merge 2 commits into
Open
docs: add Hlido to the third-party plugins acknowledgment#2095ankitkapur1992-hlido wants to merge 2 commits into
ankitkapur1992-hlido wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
WalkthroughA single ChangesREADME Plugin Mention
Estimated code review effort: 1 (Trivial) | ~2 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Hlido (https://hlido.eu) provides independent, evidence-backed trust scores for AI agents. In a NeMo Agent Toolkit environment, `pip install hlido` registers a 'hlido' function group via the nat.plugins entry point, exposing hlido__trust_check / hlido__find_trusted / hlido__verify_claim / hlido__get_scorecard so a workflow can vet another agent before delegating to it. Public API, no key required. Signed-off-by: Ankit Kapur <ankit@hlido.eu>
ankitkapur1992-hlido
force-pushed
the
add-hlido-trust-plugin
branch
from
June 29, 2026 12:12
381b70e to
3e9ef57
Compare
willkill07
requested changes
Jul 8, 2026
Drop the extra install/description parenthetical so the Hlido entry matches the format of the other externally-managed plugins, per @willkill07 review.
willkill07
approved these changes
Jul 10, 2026
Member
|
@ankitkapur1992-hlido your commit is not signed-off https://github.com/NVIDIA/NeMo-Agent-Toolkit/pull/2095/checks?check_run_id=86351160640 |
Member
|
@ankitkapur1992-hlido I cannot merge this unless your commit is properly signed-off |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds Hlido to the third-party plugins acknowledgment in the README, alongside Tavily, Redis, and ATR. One-line change.
Hlido publishes independent, evidence-backed trust scores for AI agents ("Rotten Tomatoes for AI agents"). It registers a
hlidofunction group via thenat.pluginsentry point, so a NeMo Agent Toolkit workflow can vet another agent before delegating to, installing, or relying on it:hlido__trust_check— score (0-100), tier, verdict, incidentshlido__find_trusted— discover trusted agents for a needhlido__verify_claim— fact-check a vendor claim against independent testinghlido__get_scorecard— full claim-vs-evidence scorecardPublic API, no key required.
In a NeMo Agent Toolkit environment that's all that's needed — the
hlidofunction group auto-registers via itsnat.pluginsentry point. Then:Disclosure
I'm the founder of Hlido. This is opt-in, uses only the public Hlido API, and adds no dependencies to the toolkit (the README acknowledgment is the only change here).
A note on packaging (transparency)
Hlido's integration ships inside our umbrella package (
pip install hlido, corehlido-trust) rather than a standalonenemo-agent-toolkit-hlidodistribution — we deliberately keep one pip name across all our framework integrations. It still conforms to the runtime contract:nat.pluginsentry-point group, entry pointnat_hlido, registered_typehlido, andhlido__*tool names. Verified end-to-end: in a NeMo environmentpip install hlidomakes the toolkit discover the function group.If you'd prefer we conform to the
nemo-agent-toolkit-<provider>/nat.plugins.<provider>naming convention before listing (or would rather phrase/relocate the acknowledgment differently), I'm happy to adapt — just let me know.Signed-off-by per the DCO.
Summary by CodeRabbit
pip install "hlido[nemo]".