Ligis — Counterparty Credentials
From its catalog listing
Verify that a payee holds a live, third-party-issued, revocable on-chain capability credential before your agent pays them. Hermes agents pay other agents, and the destination address comes from the HTTP answer asking for the money — nothing in the x402 flow ties that address to anything the payee has proven about itself, which is the gap ERC-8478 states in spec form. ligis reads the credential registry directly over read-only JSON-RPC and answers the question the payment flow leaves open: is this counterparty entitled to this? Five tools (ligis_check_capability, ligis_capability_hash, ligis_verify_payee, ligis_verify_payment, ligis_chains) plus two surfaces: a pre_tool_call gate that intercepts payment-shaped tool calls and escalates to Hermes's approval prompt when the payee cannot be credentialed, and a transform_tool_result hook that annotates an x402 402 challenge with the payee's credential verdict before the agent signs. The registry lets anyone issue a credential for any subject, so a live credential only counts when a trusted issuer signed it: the operator's trusted_issuers setting is the sole root of trust — tool arguments can narrow it, never widen it — verified on-chain with isCapableFromIssuer. Before its first read the plugin probes eth_chainId and eth_getCode on the registry address, so an endpoint serving the wrong chain or an address with no contract reads as unknown rather than an answer. A capability is indexed by the keccak-256 hash of its name, so the same capability resolves to the same bytes on every chain. No key, no hosted service, no secret scope.
Good to know before installing
makes read-only HTTPS JSON-RPC calls to fixed public testnet RPC endpoints (https://testnet-rpc.monad.xyz for monad-testnet, https://atlantic.dplabs-internal.com for pharos-atlantic); the RPC operator sees the caller's IP address and the queried registry, subject and issuer addresses; it holds no keys, signs nothing, sends no transactions, reads and writes no files, runs no background processes, and has no telemetry. A credential counts only when its issuer is in the trusted_issuers setting; with none configured every credentialed payee is escalated. The pre_tool_call hook escalates to Hermes's approval prompt, and --yolo and approvals.mode: off auto-approve those escalations while cron follows approvals.cron_mode; set mode: enforce to block outright. If the registry cannot be read, or a payee does not fit the hook's time budget, the call is not gated.
From its catalog listing.
How to install
- Install it. Hermes asks for any API keys it needs, then asks whether to turn it on.
hermes plugins install ligis - Said no? Turn it on later:
hermes plugins enable ligis - Restart Hermes so it loads the plugin.
Some plugins also need a sign-in or settings: see Full setup & settings. Memory plugins ask whether to become your memory provider instead. Steps follow the official plugins guide (opens in a new tab).
- Category
- Security & privacy · Work & business
- Maintained by
- sneldao (Community)
- Needs
- No API keys declared
- Adds tools
ligis_check_capabilityligis_capability_hashligis_verify_payeeligis_verify_paymentligis_chains- Adds hooks
pre_tool_calltransform_tool_result- Needs Hermes
- 0.23.1 or newer
- Version
- 0.1.0
- In the catalog
- 2026-11-14
Using the Hermes desktop app? See where plugins live

Full setup & settings ↗Source code ↗
More in security & privacy
All security & privacy plugins
New Hermes Agent updates every day on X. Follow @HermesWatcher