Compliance & onboarding · KYB
Screen a counterparty before money moves.
A new vendor or customer arrives as a name and a promise. Give Ahel the company or domain and get back its registry record, ownership chain, officers, and a sanctions/PEP screen — every field sourced, in one call. Run it here, or let your AI run it over MCP.
What one call returns
One entity, fully assembled.
Legal name, registration number, jurisdiction, and live status — straight from the official business register.
Shareholders, beneficial owners, and the GLEIF ownership graph, resolved automatically to one entity.
The entity and its owners screened against the consolidated watchlists — a hit is decisive, a clean screen is evidence.
A source and a confidence score on every fact, so the result drops straight into a case file — evidence, not a guess.
Worked example
One signal in, one entity out.
A vendor arrives on an onboarding form as a stale trading name. Ahel resolves it to the current registered entity — registration number, LEI, and live status — each field carrying its source.
Wise plcThe call your AI makes
One MCP tool call. Sourced JSON back.
The same screen your compliance team runs, as one tool call your agent makes itself — no scraping, no glue code.
// your agent calls this over MCP (mcp.ahel.ai — one endpoint, all sources)
search_company(query: "Wise plc")
// → resolved entity, every field carrying its source
{
"query": "Wise plc",
"resolved": "Wise Limited",
"fields": {
"Status": "active",
"Registration": "13211214 · Companies House",
"LEI": "213800LD9XCHIC1C4V71"
},
"sources": 3
}Same call over REST — POST api.ahel.ai/v1/search/company — or the SDK ahel.search("company", "Wise plc").
More use cases
The same engine, other decisions.
Put it in your onboarding flow.
One API key, or one MCP connection so your assistant screens every counterparty itself. Registries first, sourced end to end.