Sales & GTM · research
Know the company behind a lead before you reach out.
A company name or email domain resolves to the registered entity behind it — legal name, registration number, jurisdiction, and live status — so outreach and routing start from facts, not a guessed template.
What one call returns
One entity, fully assembled.
Official registered name, number, jurisdiction, and status behind the email domain.
Live registry status, incorporation date, and jurisdiction — is the company real, active, and where it claims to be?
Ownership, size signals, and related entities to qualify and route the lead.
A source and confidence on every fact, so your CRM starts from verified data.
Worked example
One signal in, one entity out.
An inbound lead resolves to its company entity — legal name, register, and firmographics — so your CRM and your AI enrich it the moment it lands.
Bolt Technology OÜThe call your AI makes
One MCP tool call. Sourced JSON back.
Enrich a lead the instant it lands: one call from your CRM's AI, a clean company entity back.
// 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.
Enrich every lead from one detail.
One API key, or one MCP connection so your AI runs it itself. Registries first, sourced end to end.