Company Lookup — Unified Company Card (Tech Stack + Registry)

Give it a domain or a company name and get back one unified company card: detected tech stack and scraped identity for a domain, or an official registry record for a name — built for a human to read or for an AI agent to reason over in one shot, without gluing two separate tools together.

The problem

Sales tools and AI agents need a "who is this company" answer made of several separate lookups today: a scraper for the site's tech stack, a different tool for the official registry record, and glue code to merge them into something an agent can actually use in one shot.

What you get

• One card per domain or name — tech stack and registry identity merged, no separate tools to wire together.
• Domain input → detected tech stack (CMS, ecommerce platform, key technologies — same detection engine as tech-stack-detector), plus the company name and description scraped off the homepage.
• Name or LEI input → an official GLEIF registry card: legal name, jurisdiction, status, legal form, address.
• Scored, not guessed, registry matches. Every name match is scored for similarity; only a confident match is returned as registry (see below).
• Runs on Apify: schedule it, monitor it, call it from the API or the MCP server, export to JSON, CSV or Excel, or push results straight into your own pipeline.

Registry matching — why you sometimes get a list instead of an answer

GLEIF's name search is a fuzzy relevance search, not an exact-match lookup. Taking its first hit as "the company" is how a card used to end up carrying a parent holding company's LEI and address instead of the actual business — "Monzo Bank Limited" naively resolves to "MONZO BANK HOLDING GROUP LIMITED", a different legal entity.

So every candidate name is scored against your input, and:

• Score ≥ 0.85 → accepted automatically. The card carries registry plus registryMatch: {confidence, basis, matchedName, matchedFrom} so you can see exactly what matched and how sure the match is.
• Score < 0.85 → no registry. Instead you get up to 5 registryCandidates ({lei, legalName, jurisdiction, score}) and found: false (for a name-only input) — a short list of "did you mean" entities instead of a confident-looking wrong answer.

For a domain input, this only affects the registry half of the card: the tech-stack detection and scraped company name/description are still returned and billed even when the registry match is inconclusive — only the registry block stays empty and registryCandidates carries the shortlist.

To get a guaranteed exact match: pass the full legal name (not a brand name), add a two-letter country hint after a pipe — "Alpha Payments | GB" — since the same name can exist as unrelated entities in different countries, or pass the 20-character LEI directly, which needs no name search at all.

How to run it

1. Click Try for free — no card needed on the free plan.
2. Paste domains or company names into Companies, one per line — stripe.com, Monzo Bank Limited. Add a country hint after a pipe ("Monzo Bank Limited | GB") to pin the registry match to one country, or pass a 20-character LEI directly for an exact record with no matching involved.
3. Press Start. Results appear in the dataset — read them in the UI, pull them from the API, or have a webhook push them onward.

Pricing

Pay-per-event: $0.005 per run start + $0.005 per result. No monthly seat, no minimum. 100 companies looked up cost about $0.51; 1,000 about $5.01.

A domain whose homepage can't be reached is found: false and not charged. A name-only input that comes back as a candidate list instead of a confident match (see above) is also found: false and free — you only pay once you get a real answer. A domain lookup with an inconclusive registry match is still billed, because the tech-stack half of the card is real and delivered; only the registry block stays empty.

Input

Field	Required	What it does
companies	yes	Domains (stripe.com), legal names (Monzo Bank Limited) or 20-character LEIs. One row per entry. Add a country hint after a pipe — "stripe.com | US" — to pin the registry match to one country. An LEI is used as-is, no name search. Up to 100 per run.
maxConcurrency	no	How many entries to process in parallel, 1–30 (default 10).

{
    "companies": [
        "stripe.com | US",
        "Monzo Bank Limited | GB"
    ]
}

Output

One row per input. This is a real row from a real run:

{
    "input": "stripe.com | US",
    "found": true,
    "companyName": "STRIPE, LLC",
    "domain": "stripe.com",
    "description": "Stripe is a financial services platform that helps all types of businesses accept payments, build flexible billing models, and manage money movement.",
    "registry": {
        "lei": "549300CLHGIPTCYHQ143",
        "jurisdiction": "US-DE",
        "status": "ACTIVE",
        "legalForm": "HZEH",
        "address": "C/O THE CORPORATION TRUST COMPANY, CORPORATION TRUST CENTER, 1209 ORANGE ST, WILMINGTON, US-DE, US, 19801"
    },
    "registryMatch": {
        "confidence": 1,
        "basis": "name+country",
        "matchedName": "STRIPE, LLC",
        "matchedFrom": "Stripe"
    },
    "registryCandidates": [],
    "tech": {
        "cms": null,
        "ecommerce": null,
        "technologies": ["Next.js", "Nginx"]
    },
    "checkedAt": "2026-07-26T13:57:27.363Z",
    "summary": "STRIPE, LLC — stripe.com, 2 tech detected, US-DE entity, LEI 549300CLHGIPTCYHQ143, status ACTIVE, registry match confidence 1.00."
}

Field	What it means
found	Whether the lookup returned anything usable — false means not billed
companyName	Best-known name — GLEIF legal name when matched, otherwise the scraped/site name
domain / description	Only populated when the input was a domain
registry	GLEIF card {lei, jurisdiction, status, legalForm, address} — null until a match clears the 0.85 confidence bar
registryMatch	{confidence, basis, matchedName, matchedFrom} — basis is lei, name, name+country, ambiguous or none
registryCandidates	Up to 5 {lei, legalName, jurisdiction, score} — populated instead of registry when nothing cleared the confidence bar
tech	{cms, ecommerce, technologies} — only populated when the input was a domain
summary	Human-readable one-liner

Related tools

Related tools for adjacent workflows in B2B lead generation and data enrichment.

Actor	What it does
Company Registry Enricher	Pair it in the B2B lead generation and data enrichment workflow: Turn a company name, LEI or UK company number into an official registry card: legal name, status,...
Website Tech Stack Detector	Pair it in the B2B lead generation and data enrichment workflow: Detect the technologies a website runs — CMS, ecommerce platform, analytics, marketing/CRM, JS framework,...
B2B Lead Enricher	Pair it in the B2B lead generation and data enrichment workflow: Turn a list of company websites into sales-qualified lead cards: detected tech stack, a rough revenue...
Tech Stack Change Detector	Pair it in the B2B lead generation and data enrichment workflow: Detect a website's current technologies (CMS, ecommerce, analytics, marketing/CRM, framework, hosting/CDN,...
Counterparty Risk Rollup — Sanctions, Courts, Registry, Hiring	Pair it in the B2B lead generation and data enrichment workflow: One call, one row per counterparty: sanctions screening (OFAC + EU), legal-entity registry (GLEIF),...

FAQ

Why did I get a list of candidates instead of an answer? Your input's closest registry match scored below the 0.85 confidence bar — usually because the name is a brand, not a legal name (e.g. "Monzo" instead of "Monzo Bank Ltd"), or because several entities share that name in different countries. Pass the full legal name, add a country hint, or pass the LEI directly for a guaranteed exact record.

Does it need an API key / login? No — both the tech-stack detection (public HTML/headers) and the GLEIF registry lookup are free and keyless.

How fresh is the data? The tech stack is read live off the current homepage. GLEIF publishes a daily "golden copy" of registry data.

Can I call it from an AI agent? Yes — it's a standard Apify Actor, callable via the Apify API or the Apify MCP server.

What this is NOT. It is not a KYC/AML report, a credit check, or a company-search engine — it's one card per input you already have, built from public tech signals and one public registry. It also does not guess: a low-confidence registry match returns candidates, not an entity.

Found a wrong result, or need a check we don't run? Open an issue on this Actor's page.

---

Built by zinin. Questions? Telegram @timzinin.