Entity & counterparty data
with Hermes Agent.
Drop Entity & Counterparty Data into Hermes Agent as a single resolution skill. Pass in any company name, identifier, or LEI (Legal Entity Identifier) and Hermes returns the verified legal entity, its LEI, the full corporate hierarchy — parents, subsidiaries, ultimate parent — and the ownership structure around it. Per-flow budget caps respected. Billed per call, no registry license.
Real Hermes flows that rely on this skill.
Each pattern below is a single Hermes Agent flow with Entity & Counterparty Data registered as one skill. The flow only spends when it resolves a result.
Match every inconsistent name to the one verified legal entity.
A Hermes trade or payments flow picks up each counterparty reference as it arrives, calls Entity & Counterparty Data to resolve the name or identifier to the verified legal entity, attaches the LEI, and writes the clean record back — before any downstream processing touches it. Counterparty names that arrive abbreviated, misspelled, or aliased resolve to the same verified entity every time.
Verify a new client or vendor and pull its structure on the spot.
A Hermes onboarding flow triggers on each new counterparty, calls the skill to verify the entity and retrieve its full corporate hierarchy and ownership chain, and feeds the result into Know Your Business (KYB) and due-diligence checks — all in a single flow run. No manual research pass, no overnight data refresh.
Aggregate exposure to the real controlling parent, not just the trading name.
A Hermes credit or risk flow queries each entity in the exposure book, retrieves the full ownership chain — direct owners, intermediate holding companies, and ultimate parent — and rolls exposure up to the controlling group. Concentration risk that sits behind different legal names becomes visible before it becomes a limit breach.
Resolve the real entity before the watchlist check runs.
A Hermes compliance flow resolves each counterparty to its verified legal entity and ownership structure before passing it to a sanctions or watchlist check. Screening the verified entity — not the alias or abbreviation — cuts false positives and reduces missed hits in a single extra step.
Verified entity record out, inside every Hermes flow.
Register one skill and your Hermes Agent flow resolves any counterparty to a clean, verified entity record on demand. Idle flows cost zero. That's the entire deal.
- Single Hermes skill
- Flow caps honored
Hermes Agent specific questions.
If something below doesn't cover your case, ping us — we work directly with Hermes Agent builders, no sales process.
How does this register as a Hermes Agent skill?
+
It's a single POST endpoint with a typed body. You register it in Hermes the same way you'd register any HTTP skill — endpoint, schema, price-per-call. Hermes Agent uses the price to plan flow budgets and to show what each entity resolution will cost before the skill fires.
Can Hermes Agent resolve a batch of counterparties in one flow run?
+
Yes. A Hermes flow can iterate over a list of counterparty references, call the skill per entity, accumulate resolved records, and pass the enriched batch downstream — all within a single flow execution and a single budget cap.
Does Hermes Agent need a long-lived login to call the skill?
+
No. The skill is billed per call with no long-lived credentials to manage, leak in flow logs, or rotate.
What happens when a Hermes flow hits its budget cap mid-batch?
+
The API returns resolved records for entities matched so far and stops. Hermes treats this as a normal skill result so the flow can decide whether to request more budget, process the partial batch, or queue the remainder for a follow-up run.
Can Hermes call this skill in real time, not just in scheduled batch flows?
+
Yes. The skill responds in under a second, so a Hermes flow triggered by a trade event, a new counterparty webhook, or an onboarding submission can resolve an entity in real time — one call per entity, billed per resolved result.
How is this different from giving Hermes access to a full entity registry?
+
A registry subscription doesn't fit Hermes Agent's skill model — the skill can't report a true per-call cost, so Hermes can't do real budget planning against it. Entity & Counterparty Data reports an honest per-call cost up front, which is what Hermes was designed to consume.