Fraud & risk ops · vetting
Catch the fake before it costs you.
Does this shop or domain belong to a real registered business? One call cross-checks the registry, ownership, status, and sanctions — exposing shell patterns, dead registrations, and sanctioned owners in a single pass.
What one call returns
One entity, fully assembled.
Whether the shop/domain maps to a live, registered legal entity — or a dead/absent one.
Who is actually behind it: shareholders, beneficial owners, and linked entities.
The entity and its owners screened against the consolidated watchlists in the same pass.
A source and confidence on every fact — evidence you can act on, not a hunch.
Worked example
One signal in, one entity out.
A domain on a suspicious invoice resolves to its registration record — age, registrar, and expiry — the signals that separate an established counterparty from a week-old shell.
wise.comThe call your AI makes
One MCP tool call. Sourced JSON back.
Screen a counterparty's infrastructure inline — your agent calls it the moment a domain looks off.
// your agent calls this over MCP (mcp.ahel.ai — one endpoint, all sources)
search_domain(query: "wise.com")
// → resolved entity, every field carrying its source
{
"query": "wise.com",
"resolved": "wise.com",
"fields": {
"Registered": "1994-03-07",
"Registrar": "101domain GRS Limited",
"Expires": "2028-03-08"
},
"sources": 1
}Same call over REST — POST api.ahel.ai/v1/search/domain — or the SDK ahel.search("domain", "wise.com").
More use cases
The same engine, other decisions.
Vet every merchant automatically.
One API key, or one MCP connection so your AI runs it itself. Registries first, sourced end to end.