A company enrichment pipeline often begins with an innocent join: read a homepage name, find a similar registry name, and place the registry identifier beside the domain. The join can look convincing while the underlying relationship remains unverified. A brand, a subsidiary, a trading name, and a legal entity can share words without being interchangeable.
Company Lookup build 0.3.1 keeps that distinction visible. It accepts domains, legal company names, or exact LEIs and returns public website and GLEIF observations with source evidence. Its job is to prepare a reviewable company card. It does not turn a name match into domain ownership or a completed identity check.
Choose an input that matches the question
For a website observation and a separate legal-name search, an illustrative input is:
{
"companies": [
"stripe.com | US",
"Monzo Bank Limited | GB"
],
"maxConcurrency": 2
}
This example demonstrates the schema; it is not a claim about fresh responses from either company. The input accepts up to 100 company strings. A two-letter country hint after the separator helps distinguish similarly named entities in different jurisdictions. If an exact LEI is already known, submitting that identifier makes the registry retrieval question more precise.
Choose a full legal name when that is the identity you need. A short brand label creates a different and more ambiguous search. The Actor accepts a URL for convenience but canonicalizes website identity to the hostname. Different paths on a company's site therefore do not become separate legal entities.
Read three confidence questions separately
Website evidence, legal-entity evidence, and the association between them deserve different columns. A reachable homepage can support a strong website observation. An exact registry retrieval can support a strong registry identity. Neither alone proves that the registry entity owns the submitted website.
The delivered record exposes this distinction with websiteIdentityConfidence, registryEntityConfidence, domainRegistryAssociationConfidence, and domainRegistryLinkStatus. In particular, unverified_name_based_association describes a name-based connection awaiting verification. Do not average the separate confidence fields into an attractive-looking master score that conceals the weak association.
A review action such as VERIFY_DOMAIN_TO_LEGAL_ENTITY_LINK is useful precisely because it leaves the unresolved step visible. Preserve source URLs, observation time, registry identifiers, candidate records, and data gaps in the exported card. A downstream reviewer should be able to reconstruct why the association was proposed.
Do not let deduplication invent identity
The installed contract deduplicates supported domain and URL variants and case-only name or LEI variants. That prevents repeated equivalent requests from inflating the batch. It does not authorize merging two different companies because their names are similar.
Maintain the original requested value beside the normalized identity. When a registry search is ambiguous, keep candidate records separate from an accepted entity. A failure or an ambiguous candidate row is not a verified company card. Conversely, a delivered website observation may be useful even when the domain-to-registry association still needs human review.
A useful validation exercise contains an exact LEI, a full legal name with a country hint, two equivalent URL variants, and an ambiguous short name. Inspect whether equivalent requests are deduplicated and ambiguous candidates stay outside a canonical entity assignment. This is an acceptance plan, not a report of a new cloud run.
The website component reads the submitted homepage's initial HTML and response headers. It cannot establish a complete technology inventory, private ownership records, or what has changed since observation. Registry status is also an observed source value, not a guarantee of commercial reliability. Put the card into a staging layer and require explicit evidence before promoting a proposed domain-to-entity relationship into a system of record.
Cost and source boundary
The live FREE-tier event prices checked on 20 October 2026 are $0.005 per result-found event and $0.005 per automatic Actor-start event. The start event is memory-scaled: one event per GB, with a minimum of one event. A free result outcome therefore does not make an entire run free. Other account tiers have their own rates; check the live pricing panel before execution. These prices describe the installed contract, not measured customer revenue or a new runtime test.
Inspect the Actor, input, and current pricing.
AI-assisted drafting; technical statements reviewed against the installed Actor source and current API metadata. Examples are illustrative unless explicitly identified as saved observations.
Top comments (0)