Finance & investing · diligence
Diligence a target in minutes not days.
Filings, beneficial owners, linked companies, and risk signals on any entity — assembled from primary sources and scored, before the first meeting. Give Ahel the company or domain and get one resolved profile back.
What one call returns
One entity, fully assembled.
Registration, legal form, status, and the latest financial filings — straight from the register.
The ownership chain and ultimate beneficial owners, resolved to one entity via GLEIF.
Related companies, shared officers, and the corporate structure around the target.
Sanctions/PEP exposure on the entity and its owners, each finding sourced and scored.
Worked example
One signal in, one entity out.
A counterparty on a term sheet resolves to its official register entry — jurisdiction, registration, and incorporation date — so credit and exposure checks start from ground truth, not a name.
Bolt Technology OÜThe call your AI makes
One MCP tool call. Sourced JSON back.
Drop entity resolution into your diligence workflow: one call, structured JSON, every field carrying its source.
// your agent calls this over MCP (mcp.ahel.ai — one endpoint, all sources)
search_company(query: "Bolt Technology OÜ")
// → resolved entity, every field carrying its source
{
"query": "Bolt Technology OÜ",
"resolved": "Bolt Technology OÜ",
"fields": {
"Status": "active",
"Registration": "12417834 · e-Äriregister",
"Founded": "2013-02-07"
},
"sources": 2
}Same call over REST — POST api.ahel.ai/v1/search/company — or the SDK ahel.search("company", "Bolt Technology OÜ").
More use cases
The same engine, other decisions.
Diligence, on tap.
One API key, or one MCP connection so your AI runs it itself. Registries first, sourced end to end.